Chiefs' latest disappointment should come at no surprise
Last week the Kansas City Chiefs were set to take on the Los Angeles Chargers with just Kadarius Toney, Justin Watson, Skyy Moore, Marquez Valdes-Scantling, and Travis Kelce as the receiving options. Then, Toney left the game early with a hamstring injury. Toney's health -or lack thereof- is big reason why the New York Giants […]
Last week the Kansas City Chiefs were set to take on the Los Angeles Chargers with just Kadarius Toney, Justin Watson, Skyy Moore, Marquez Valdes-Scantling, and Travis Kelce as the receiving options.
Then, Toney left the game early with a hamstring injury.
Toney's health -or lack thereof- is big reason why the New York Giants traded the former first-rounder. In fact, the same hamstring he injured on Sunday night isn't a new injury – it's the one that came over with him.
(Or didn't come with him, according to Toney himself)
Either way, Andy Reid cleared everything up on Friday.
And, as it turned out, Toney's injury isn't a new one. It is in fact one of the same hamstring injuries he dealt with in New York.
"No, he had had it in New York, and he just felt it kind of coming back, and so we just said, 'Listen, let's not go any further with it and make it more serious," said Reid. "So, we backed off on it."
Overall, this latest hangup isn't much of a surprise. Toney had three hamstring injuries in New York, two of which have occurred since the summer. It's unclear as to which specific time the current injury is related to, but the main point is clear: Toney's hamstrings are a risky bet to stay healthy, right now.
Regardless, it's a disappointment for the Chiefs, who were receiving solid play from Toney over the last few weeks. They were also hoping he could boost the punt return production, as well.
All of that is obviously on hold, for now.
Featured Image Via Denny Medley-USA TODAY Sports
[totalpoll id="161924"]
