search_channels

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

No annotations are provided, so the description must disclose behavior. It only states the search purpose, not details like how live_only filters results, whether limit caps output, or what happens when no matches are found. This lack of behavioral context could lead to incorrect invocation.

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 two succinct sentences, front-loaded with the primary action and then the use case. Every word is useful, and there is no redundancy or filler.

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 has 3 parameters and no output schema, and the description is minimal. It clarifies the core search purpose but omits how filters like live_only affect behavior and what the response looks like. The gaps are notable for an agent selecting parameters, though the tool is relatively simple.

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 provides 100% description coverage for all parameters, so the baseline is 3. The description adds no additional meaning beyond the query term, saying nothing about limit or live_only semantics. It does not compensate beyond what the schema already states.

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's function: 'Busca canales de Twitch por nombre o palabras clave' (searches Twitch channels by name or keywords). It also provides a use case ('descubrir nuevos streamers') that differentiates it from exact-lookup siblings like get_twitch_user.

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 phrase 'Útil para descubrir nuevos streamers' implies the tool is for exploratory search rather than exact user lookup. It offers clear context but does not explicitly name alternatives or exclusion criteria, such as 'for exact user info, use get_twitch_user instead.'

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