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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered. The description adds real behavioral context beyond that: the 0-100 scoring scale, the comparison baseline (best possible squad, 5-gameweek horizon), and that the output names specific players to fix. It doesn't discuss failure modes for invalid/unknown IDs, so not a 5.

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?

Two sentences, front-loaded with the trigger condition, then the output contract and input options. No filler or redundancy.

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?

No output schema exists, so the description must carry the return-value burden, and it does describe the score and named fixes. Inputs are fully covered by the schema plus description. It omits edge-case handling (what happens if the ID is invalid or fewer than 11 players are given), leaving a small gap.

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%, so the baseline is 3. The description adds value by clarifying the three mutually alternative input routes and that players can be read from a screenshot with club suffixes for disambiguation, which the schema only partially conveys. Slightly above baseline.

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+resource ('rate/review a Fantasy Premier League team') and elaborates the mechanism: a 0-100 score against the best possible squad over the next 5 gameweeks plus a list of biggest fixes. An agent can distinguish this from siblings like get_my_team or compare_players from the description 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?

'Use this when a manager wants their team rated or reviewed' gives clear triggering context, and it enumerates the acceptable input paths (team ID, FPL link, or names from a screenshot). It does not name an alternative tool or state any exclusions, so it stops short of a 5.

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