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

Annotations already cover readOnly/destructive safety, so the description's job is incremental. It does add real context: the external data source (ESPN) and the fact that it is the *current* roster, which explains the non-idempotent hint. It stays silent on failure modes — unknown or ambiguous team names, stale data, or network dependency — which matter for an external fetch.

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?

One front-loaded sentence carrying source, scope, and return contents, followed by a short clause on the input convention. No filler, no restatement of the title.

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?

For a one-parameter read tool with annotations and no output schema, the definition covers source, returned fields, and input convention — enough to call it correctly. The remaining gap is what happens when a team name isn't recognized, which an agent would likely need to recover gracefully.

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 100% and the single parameter already carries the description "The team, as the player named it," so the schema does the heavy lifting. The description's "as the player says it" restates rather than extends that, giving no extra detail on fuzzy matching, accepted formats, or examples.

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?

Specific verb plus resource plus payload: "Reads a sports team's current roster from ESPN" and names exactly what comes back (players by position with numbers, head coach). It is clear what the tool does, but it never contrasts itself with the similarly named sibling `request_team`, so an agent must guess which one to reach for.

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?

"for Plot Speaks Team Trivia" gives a situational frame, and "Takes the team's name as the player says it" hints at when/how to call it. There is no explicit when-not guidance and no routing to alternatives such as `request_team` or `game_question`, so usage is only implied.

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