steam_get_top_games

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It does not explain what 'top' means, how games are sorted, whether genreId is resolved as a name or ID, or what happens when no genreId is provided. The description only names the operation without revealing behavior.

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?

The description is a single focused sentence, with no filler or repetition. It front-loads the core purpose and includes useful examples in a compact way.

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 two-parameter list tool, the description plus schema is minimally sufficient. However, with no annotations and no output schema, it leaves gaps around what 'top' means, the effect of an omitted genreId, and the shape of the response.

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 descriptions provide 100% coverage for both parameters, including the default for limit and the name-or-ID nature of genreId. The description adds slight value with genre examples and the phrase 'category or genre', but it does not significantly extend the schema semantics.

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 states the tool's function: browsing top games for a specific Steam category or genre. It gives concrete examples like 'Action', 'RPG', and 'Strategy', which makes the resource and scope easy to identify. However, it does not explicitly differentiate from the sibling tool steam_get_top_sellers.

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?

The description provides a clear use case: when you want to browse top games within a specific category or genre. It does not mention alternatives or exclusion criteria, but the context is explicit enough that an agent can infer when to invoke it.

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