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

Annotations declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds non-obvious behavioral context the annotations don't: internal heat scores are deliberately omitted from the response. It could say more about the result ordering or freshness window, but it meaningfully augments the annotations.

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 clauses, all front-loaded and information-dense: what it returns, when to use it, and when to use the sibling instead. No filler.

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 single-param, read-only, no-output-schema list tool, the description fully covers purpose, alternative routing, and an important response caveat. Nothing an agent needs to call it correctly 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?

There is only one parameter and schema coverage is 100% – the schema documents limit's range (1–10) and default. The description adds nothing beyond the schema about limit, so baseline 3 applies.

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 ('Get the current Gameshot Top 10') with the added detail that each event carries a one-based rank. It explicitly distinguishes itself from the sibling gameshot_get_latest by naming it.

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 concrete use case ('what is hot now', discovering valid story public IDs) and names the alternative tool with the condition that selects it ('use gameshot_get_latest for a chronological news list'). This is explicit when-to-use/when-to-use-other guidance.

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