channel_select

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

Description only reveals that exclusive=True deselects others. No disclosure of side effects, error handling (e.g., invalid index), or state changes beyond selection. With no annotations, the burden is higher, and this falls short.

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?

Single sentence, no extraneous text. Front-loaded with action and key parameter behavior. Efficiently conveys core information.

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 simple select action with no output schema, the description covers the essential behavior but omits details like return value, invalid index handling, and what 'select' visually or functionally entails. Adequate but not thorough.

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 0%, so description must compensate. It explains the exclusive parameter's effect but says nothing about 'index' (what values are valid? 0-based or 1-based?). Only partial addition of meaning.

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?

Description clearly states the action (select a channel) and mentions the exclusive parameter. It distinguishes from sibling tools like 'channel_selected' (which likely gets selection) and 'arrangement_select', but could be more explicit about what 'channel' means in context.

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?

No guidance on when to use this tool vs alternatives (e.g., channel_mute, channel_solo). No prerequisites or when-not-to-use instructions. The exclusive parameter hint is helpful but insufficient for usage decisions.

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