mixer_set_send_level

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

With no annotations, the description must disclose behavioral traits. It states a write operation but lacks details on side effects (e.g., overrides existing sends, requires existing routing) or error handling (invalid track indices). The range 0..1 is useful but insufficient.

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?

A single concise sentence front-loads the action and scope. No filler, every word contributes meaning.

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 but lacks critical context: no mention of return value, error conditions, or whether it creates a send route if absent. Given no output schema or annotations, the description should cover these basics.

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 the description should compensate. It only explains the 'level' range (0..1) but does not describe 'src_track' or 'dst_track' semantics, leaving the agent to infer their roles from the tool name.

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 specifies the verb 'Set' and the resource 'send level from one mixer track to another', including the value range (0..1). This uniquely identifies the tool among sibling mixer tools that set volume, pan, etc.

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 versus alternatives, nor prerequisites or exclusions. For instance, it does not mention whether a send must already exist or if the tool creates one, leaving the agent uncertain about preconditions.

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