get_top_games

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

No annotations are provided, so the description bears responsibility for disclosing behavior. It discloses that the list is sorted by viewer count and current, but does not describe the return format, authentication needs, or rate limits. This is a read-only operation, so risk is low, but additional context would be helpful.

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?

One clear, declarative sentence with no fluff. It front-loads the verb and subject.

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 a simple list retrieval with one optional parameter. The description covers the core behavior (what, where, sorting). Since there is no output schema, the return structure is not detailed, but that's not a major gap for such a simple tool.

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 fully documents the only parameter 'limit' with default, min, max, and a Spanish description. The tool description adds no extra parameter detail beyond the schema, but the baseline for high schema coverage is 3.

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 retrieves the most popular Twitch games sorted by viewer count, using specific verb 'Obtiene' and resource 'juegos más populares en Twitch'. It distinguishes from sibling tools like get_top_streams (streams vs games) and get_game_info (list vs specific).

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 the tool is for retrieving a ranked list of the most popular games currently on Twitch. It does not explicitly name alternative tools or exclusion criteria, but the scope is clear enough to separate it from top streams and game-specific info.

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