steam_top_sellers

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

With no annotations, the description carries full burden. It states the tool is 'credential-free' and 'public', but does not disclose rate limits, caching, or any potential side effects. It adds some value but could be more transparent.

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 mostly concise but has redundancy: 'Get...' and 'Returns...' say essentially the same thing. Could be tightened without losing meaning.

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?

Given no output schema and no annotations, the description explains return contents and the 'cc' parameter well, but omits explanation of 'l' and lacks usage examples or prerequisites. Adequate for a simple tool but with clear gaps.

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 description adds context for the 'cc' parameter (affects currency and sales ranking) but does not explain the 'l' parameter beyond the schema. Overall, marginal added value over 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 states it retrieves Steam's weekly top-sellers chart for a country, specifying the resource (top-sellers chart) and action (get). It distinguishes from sibling tools like steam_app or steam_search by being explicitly about the top-sellers chart.

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 implies usage for getting weekly top-sellers by country but does not indicate when to use this tool over others (e.g., steam_featured, steam_charts_most_played). No explicit alternatives or exclusions are provided.

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