get_top_streams

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

With no annotations, the description carries full burden for behavioral disclosure. It only indicates a read operation ('obtiene') and that results reflect current popularity, but it does not mention return format, pagination limits, default sorting, rate limits, or what happens when no parameters are provided. This is a significant gap for an unannotated tool.

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 concise sentence that states the primary function first, then mentions the two optional capabilities. It contains no redundant wording and is easy to parse quickly.

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?

While the core purpose is clear, the description lacks guidance on when to use the tool, what the returned data looks like (since there is no output schema), and behavioral details. For a simple 2-parameter tool, this is minimal but leaves an agent uncertain about expected return values and edge cases.

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%: both 'limit' and 'game_name' have clear descriptions in the schema. The tool description adds only a brief reference to 'filtrar por juego y limitar resultados,' which partly mirrors the schema but does not provide extra meaning beyond it. Baseline of 3 is appropriate.

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 the most popular Twitch streams at the current time, using the verb 'obtiene' and specifying the resource 'streams'. It also distinguishes itself from siblings like get_top_games and get_user_videos by focusing on streams and mentioning optional filtering by game and result limiting.

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 current popular streams and mentions filter/limit options, but it does not explicitly state when to prefer this tool over alternatives such as search_channels or get_user_videos. No exclusion criteria or alternative tool recommendations are given.

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