send_set_mute

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

Minimal description without annotations. Does not disclose what happens if send doesn't exist, whether operation is idempotent, or any side effects beyond setting mute.

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?

Extremely concise: 5 lines with clear arg list. No wasted words.

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?

Nearly complete for a simple boolean setter with 3 required params. Lacks error handling details, but sufficient for basic use. No output schema needed.

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?

Adds meaning beyond schema: explains 'mute: True=mute' and identifies parameters as 'Source track' and 'Send index'. Could be more precise (e.g., indexing convention) but clarifies basic intent.

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?

Clearly states 'Mute/unmute send.' with specific verb and resource. Among sibling tools like send_set_pan and send_set_volume, it uniquely handles mute state.

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., other send modifications). No prerequisites or context for correct usage.

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