send_add

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

With no annotations, the description carries the full burden. It states the result ('Emits a real <PLUGIN type='auxsend'/> element') and clarifies the amount_db effect ('proper slider position'). It does not detail edge cases (e.g., conflicting parameters), but the core behavior is transparent.

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 two sentences, front-loads the purpose, and packs all essential guidance without redundancy. 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?

It explains the two parameter modes, the bus range, the companion tool (aux_return_add), and the resulting element. This fully situates the tool within the DAW workflow and sibling tools, covering all needed context for correct use.

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 description coverage is only 20% (dest_track_id). The description compensates by explaining bus_num vs dest_track_id, src_track_id ('on a track'), and amount_db ('slider position'), but leaves pre_post unexplained. Since pre_post is an enum, its values are visible but its meaning (pre/post fader) is not clarified.

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 ('Add'), the object ('aux send'), and the context ('on a track'). It differentiates from sibling tools by specifying 'parallel routing' and referencing aux_return_add, making its unique role unmistakable.

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?

Explicitly instructs when to use bus_num versus dest_track_id ('pass bus_num explicitly, or pass dest_track_id to auto-pick a bus'), notes the valid bus range (0..15), and advises pairing with aux_return_add. This leaves no ambiguity about how to invoke the tool.

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