clock menu more-arrow no yes

Filed under:

NFL Free Agency 2013: Jared Cook just isn't a receiver

New, comments

The Titans had a tough call to make after Jared Cook decided he would challenge his designation as a tight end if he was tagged. I think they made the right call.

John Grieshop

The more I think about it, the more ridiculous it is that Jared Cook was going to challenge his designation as a tight end if the Titans tagged him as a tight end. Just a little note on that, had the Titans tagged him and the case gone to arbitration, they would have been able to remove the "tender" if Cook had not signed it and he won the case. However, if he signed it, which he would have, the Titans would have been on the hook for whatever the arbitrator decided.

That being said, it is insane that he might win his case that he is a wide receiver. While the numbers showed that he lined up wide more than he did tight, that doesn't make him a receiver any more than sitting in a hen house would make me a chicken. $10 million for Cook for one year would have been the worst NFL contract since the Titans franchised Bo Scaife.

It is going to be interesting to see what contract he ends up signing. If he is entering free agency with the idea that he is going to get paid like a receiver, it is going to be a sad day for him when the offers start coming. He will get a big contract from someone, but he isn't going to get paid like a receiver...nor should he.

You can make the argument that Cook as much star potential as anyone on this roster, but four years is long enough for potential to translate into ability. If we are being honest, Cook's never did.

Now we get to sit back and watch what happens to him at his next stop. He and his agent would have you believe that his lack of consistent production with the Titans was a product of the coaching staff here not knowing how to use him. We will find out if that was true or not in 2013.