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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds freshness ('Refreshes every 3 hours') and notes that ranks include injuries, which the agent would not otherwise know. It does not discuss auth or what happens when no rows match, but the annotation coverage lowers the burden.

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 purpose and view split, and every clause carries real information since there is no output schema to describe fields. However, it is one dense run-on paragraph with long field enumerations that would be easier to scan if segmented.

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 and zero required parameters, the description carries the full burden of explaining returns, and it does so field-by-field for both views, including edge definitions and tier vocabularies. An agent has enough to call it and interpret results without extra lookups.

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 coverage is 80% so the baseline is 3, and the description earns above that by explaining what 'view teams' returns versus 'view matchups' and by defining the meaning of dl_rank/ol_rank and the run-tier labels. It leaves 'side' and 'limit' semantics to the schema, which already documents both.

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 and scope: NFL OL vs DL matchups for the current week, split into two named views (matchups and teams) with exactly what each returns. An agent can tell this apart from generic siblings like invoke_nfl_game_matchup or invoke_nfl_personnel because the description names line-vs-line pressure/run-blocking ranks explicitly.

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?

Gives concrete use cases: DST picks, quarterback pocket risk and RB matchups, which tells the agent what question this tool answers. It does not name an alternative tool or state when NOT to use it (e.g., versus invoke_nfl_dvp or invoke_nfl_coverage_splits), so it stops short of full routing guidance.

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