Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), lowering the bar. The description adds the season-to-date semantics of week 0, but that is repeated in the schema and it says nothing about return shape, pagination, or how the 'plan limit' interacts with the limit parameter.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a compact two-sentence entry that leads with the resource and then the week-0 caveat. The metric list is somewhat enumerative but every item earns its place by documenting the returned fields in the absence of an output schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description usefully lists the returned metrics and notes the season-to-date behavior, which partially compensates. However, it omits any guidance on default sorting, filtering interplay, or how it differs from sibling NFL stat tools, leaving the agent without enough to choose it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 80%, so the schema already documents team, week, limit, and position, and the enum on sort_by. The description adds no syntax or format detail beyond what the schema provides; its metric list describes return values rather than parameter meaning. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource precisely ('Receiving opportunity by player') and enumerates the specific metrics returned (targets, air yards, aDOT, target share, WOPR, RACR, etc.), so an agent knows exactly what data comes back. It does not, however, distinguish this from nearby siblings like invoke_nfl_player_pool or invoke_nfl_projections, so an agent cannot route between them from the text alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no statement of prerequisites, and no mention of alternatives among the many NPLAYER/NFL siblings. The only contextual hint is 'week 0 is season to date,' which is a parameter note rather than usage guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.