Top games

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds useful context beyond that: it works without an API key and clarifies that 'hot' represents the home-page ranking, which gives the agent a clearer behavioral model.

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?

Four short, focused sentences front-load the core concept and end with practical use cases. There is no filler, though the first line could be clearer to agents unfamiliar with the 'rails' metaphor.

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 simple read-only list tool with no required parameters and rich schema coverage, the description is mostly sufficient. However, there is no output schema, and the description doesn't specify what a returned item looks like or what 'rails' contains, leaving some ambiguity for an agent.

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?

The schema covers all parameters with descriptions, so the baseline is 3. The description only repeats 'hot' as the home-page sort, adding no new parameter-level meaning beyond the schema.

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?

The description clearly establishes top_games as a ranked, read-only games list and ties it to the front page, with 'hot' as the default view. It is not a tautology and is distinguishable from search/get/management tools, though it doesn't explicitly name a sibling and 'rails' is somewhat jargon-heavy.

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?

It gives concrete when-to-use guidance: check what is doing well before building, or see where your own published game landed. It doesn't mention when not to use it or point to alternatives like search_games, so it lacks explicit exclusions.

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