steam_charts_top_releases

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

Discloses that results are app IDs only (not name-enriched), that lists are large, and that it is credential-free and public. No annotations provided, so description carries the burden well. Could mention pagination or if it returns all months at once but it's adequate.

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 sentences that efficiently cover purpose, output details, caveats, and authentication. No unnecessary text, well-structured and front-loaded.

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 tool with no parameters and no output schema, the description explains the return format, notes the need for name resolution, and confirms public access. Fully adequate for an agent to understand usage.

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?

No parameters exist in the schema, baseline is 4. Description adds no parameter semantics since none are needed.

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?

Clearly states it retrieves Steam's monthly best-new-releases index. Differentiates from sibling chart tools like steam_charts_most_played or steam_charts_concurrent by specifying it returns monthly top-releases with app IDs, month labels, and start dates.

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?

Implicitly advises when to use by describing the output (app IDs only) and suggests resolving names via /steam/items. Lacks explicit comparison with similar Steam chart tools but provides enough context for appropriate usage.

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