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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so safety is covered. The description adds value beyond that: values are fractions with a worked example (0.056 = +5.6 percent), data is 'Updated daily', and passing a team returns a week-by-week trend rather than the full-team table.

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?

Front-loaded with the purpose and the return-field inventory, followed by the units convention and team-filter behavior. It is dense from the metric list but every sentence carries information; no filler.

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 carries the return-value burden and does so by naming the fields returned and their units, plus the refresh cadence. The gaps (limit behavior, sort_dir semantics) are minor for a read-only listing tool.

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 low (25%) with 4 params, but the description clarifies the 'team' parameter's behavior (week-by-week trend) and the metric meaning of several sort_by enum values via the field list. It says nothing about limit or sort_dir, so it only partially compensates for the schema gap.

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?

States a specific resource (NFL pass rate over expectation) for a defined scope (all 32 teams this season) and enumerates the returned metrics, so an agent knows exactly what data this yields. It does not explicitly differentiate itself from metric-adjacent siblings like invoke_nfl_pace or invoke_nfl_air_yards, so it lands at 4 rather than 5.

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?

Usage is implied rather than stated: the tool returns team-level PROE and 'Pass team for the week by week trend' hints at the team-filtered mode. There is no explicit when-to-use/when-not guidance and no named alternatives among the many NFL siblings, so it is only implied.

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