steam_get_top_sellers

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

With no annotations, the description carries the behavioral disclosure burden. The phrase 'current global' adds context that the result is a live, geographically broad snapshot, and 'get' implies a read-only operation. However, it does not disclose the output format, sorting logic, or whether authentication or rate limits apply.

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 redundancy. Every word contributes meaning, and the tool's core purpose is immediately clear.

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?

The tool is simple and the schema covers its one parameter, but the description is thin for an agent selecting between similarly named siblings. It does not clarify how 'top sellers' differs from the sibling 'steam_get_top_games', and with no output schema or annotations, the description alone leaves some ambiguity about the exact result shape and selection criteria.

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 already describes the only parameter, 'limit', including its default, so schema description coverage is 100%. The description adds no parameter-level information, but none is needed beyond the schema. The baseline of 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?

The description states a clear verb and resource: 'Get the current global top selling games on Steam.' It clearly describes what the tool does. However, it does not explicitly distinguish this from the sibling tool 'steam_get_top_games', so the differentiation is left to the name and inference.

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 no guidance on when to choose this tool over its siblings, particularly 'steam_get_top_games'. There is no mention of alternatives, exclusions, or context such as 'use this for sales-based rankings rather than player-based rankings.'

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