channel_up

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

The description discloses only the basic action without any behavioral details, such as whether it wraps around at the last channel, works only with certain channel lists, or any side effects. No annotations are present to supplement this.

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 extremely concise at four words, with no unnecessary information. It is front-loaded and efficient for a simple action.

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 description is adequate for a simple channel navigation tool, but it lacks any mention of context such as supported channel types, behavior at boundaries, or confirmation feedback. Given no output schema and trivial parameters, it meets a minimal standard.

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?

With zero parameters, the baseline is 4 per the evaluation guidelines. The description does not need to add parameter information, and it does not detract from the tool's clarity.

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 'Go to the next channel' uses a specific verb and resource, clearly indicating the action. It distinguishes itself from siblings like 'channel_down' (opposite direction) and 'set_channel' (specific channel selection).

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 is provided on when to use this tool versus alternatives such as 'set_channel' or 'channel_down'. There is no indication of prerequisites, context, or when to avoid using it.

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