Brandin Cooks, WR
We’ve spent a little time on this site talking about the possibility of acquiring Texans wideout Brandin Cooks. The recently-turned-28-year-old Cooks would provide the Chiefs with an experienced, viable threat opposite Tyreek Hill—something the team hasn’t had since Sammy Watkins left in free agency last season.
The 5’10” 185-lb. Cooks has been a solid contributor for a struggling Houston squad, pulling in 45 catches for 502 yards in 7 games. He also has a very low cap number this season, under $2 million, and would easily fit within Kansas City’s books.
The primary question I’d ask any team interested in bringing in Cooks is, how do you evaluate the player for his inability to stay on a roster? Cooks has already played for four teams in his eight-year career, and if he is dealt this week, he will be on his fifth roster since 2016. Why is that? Why is there a player who has eclipsed 1,000 yards with four different teams being traded away again? It leads me to believe that there is a behind-the-scenes issue with Cooks that causes teams to ultimately give up on him. Conversely, it’s intriguing that three different teams have pulled the trigger on spending a first-round pick to secure his services (once in the 2014 draft, twice in trades).
Then there is the question of whether Cooks would be able to contribute. Like we mentioned earlier with Will Fuller, there’s little reason to believe the Chiefs would quickly plug Cooks into a large role in the offense. Cooks would also occupy another non-special-teams roster spot at wide receiver.
Cooks is a player who would probably be very productive for most teams, but there are questions swirling around this one. Given the fragility of the Chiefs’ locker room at this juncture in the season, I can’t see them adding a player with Cooks’ track record of club-hopping.
Cooks should be available for an early Day 3 pick.