mixer_select

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Focus / select a mixer track' and does not mention side effects, whether the selection persists, what happens on invalid track values, or whether the operation is read-only versus UI-mutating.

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, efficient sentence with no filler or redundancy. It gets directly to the point and is fully front-loaded.

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 one-parameter selection tool, the description is minimally viable: it names the action and the target resource. However, the complete absence of parameter semantics and behavioral detail means an agent may still guess about indexing and side effects.

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 has 0% description coverage, and the description adds only minimal context by mentioning 'a mixer track.' It does not clarify whether the integer track parameter is 0-based or 1-based, what valid ranges are, or how it relates to mixer_track_info indexing.

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 states a clear action ('Focus / select') and a specific resource ('a mixer track'), which makes the tool's purpose immediately identifiable. It also distinguishes it from related siblings like channel_select because it explicitly targets the mixer track rather than a channel.

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 provides no guidance on when to use this tool versus alternatives such as mixer_track_info or ui_selected_channel. There are no stated prerequisites, exclusions, or scenarios where a sibling would be more appropriate.

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