set_fx_send_mute

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

With no annotations, the description carries full burden. It states 'Mute or unmute' which implies a binary toggle, but does not disclose side effects (e.g., does it affect other sends?), immediacy, or whether it is destructive. Basic behavior is clear but lacks depth.

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 sentence with no extraneous words. It is front-loaded with the action and resource, and every word is necessary.

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 is simple (2 params, boolean + integer), but critical context is missing: which channel does this FX send belong to? The tool name does not specify a channel; it likely operates on a 'currently selected' channel, which is not stated. With an output schema present, return values are not needed, but the missing channel context is a significant gap for an agent.

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% (no descriptions), so the description must add meaning. It specifies that 'fx_slot' ranges from 1-4, which is not in the schema. The boolean 'muted' is self-explanatory, but no additional format or constraints are given. The added range information is valuable.

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 action ('Mute or unmute') and the resource ('FX send (slot 1-4)'). It distinguishes this tool from siblings like 'set_fx_send_fader' (adjusts level) and 'set_channel_mute' (mutes channel). The scope is precise.

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 explicit guidance on when to use this tool versus alternatives. It does not mention that this tool operates on a specific channel or provide context like 'use this to enable/disable an FX send' without mentioning constraints or prerequisites.

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