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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds useful edge-case context beyond them: a blank page with no players returns status no_data, and the source season can lag the current season. It does not cover auth or rate limits, but with annotations carrying the safety profile this is above baseline.

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?

Three sentences, front-loaded with the purpose, followed by parameter guidance and then edge cases. Dense but without obvious filler; the sort-parameter sentence could be slightly clearer, but every sentence earns its place.

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?

An output schema exists, so return values need not be explained. The description covers purpose, the required slug, optional parameters, a no_data edge case, and a freshness caveat. It is adequate for calling the tool, though it omits format details for the order and sort_by parameters.

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 0%, so the description must compensate. It clarifies that slug is a host-free salary-cap page slug, that q is a player search, and that sorting operates on all published rows, adding real meaning. It does not distinguish order from sort_by or give accepted values, leaving gaps.

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 verb and resource ('Read an NFL team's published salary-cap season...') and enumerates the returned content (team totals, player cap scenarios, expanded pay breakdown). It does not name or exclude any sibling tool, so it falls short of the explicit differentiation a 5 requires.

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 a prerequisite ('Supply the host-free salary-cap page slug') and explains optional search/sort behavior, which implies the tool's usage. However, it never states when to choose this tool over alternatives or what conditions select it, leaving routing to inference.

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