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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real behavioral context beyond that: result ordering (newest first) and the pagination cap (limit up to 100), which an agent can't infer from annotations alone. No mention of rate limits or result cardinality, hence 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?

Three tight clauses: what it returns (front-loaded), how it's filtered/paged, and when to prefer a sibling. 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?

An output schema exists, so return-value shape needs no explanation. For a three-param, zero-required read tool, the description covers scope, ordering, filtering, pagination, and disambiguation — nothing an agent needs is missing.

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% — the schema already documents the game enum, limit range 1–100 with default 20, and zero-based offset. The description restates the game list and the limit cap without adding syntax, defaults, or interaction rules, so this is 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 and resource ('Returns BO3.gg tournament MVP awards'), the ordering ('newest first'), the optional game scoping, and enumerates the payload fields (award type, tournament, player, team, article). An agent knows exactly what it retrieves without opening the schema.

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?

Explicitly routes the agent: 'Use it for who won MVP at an event; use bo3_player_stats for a player's numbers.' That names a sibling and the condition selecting it, though no negative case is given relative to other bo3_* tournament siblings (e.g. bo3_tournament_squads).

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