send_create

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

With no annotations, the description carries the transparency burden. It reveals important behavior: MIDI routing requires paired channel parameters, and audio is separate and can be muted via send_set_mute. However, it doesn't mention side effects, prerequisites, or project mutation details beyond the obvious creation action.

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 concise and front-loaded: main purpose, then batch alternative, then MIDI-specific usage, then structured args. Each sentence adds value without redundancy.

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 4-parameter tool with no annotations and no output schema, the description covers the core functionality and parameter semantics thoroughly. Minor gaps include lack of index convention (0-based vs 1-based) and no mention of return value or error behavior, but these are not critical for basic invocation.

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 0%, so the description fully compensates. Every parameter is explained: source_track and dest_track are indexes, midi_source_channel/dest_channel have ranges (0=all, 1-16) and a pairing constraint. This adds significant meaning beyond the bare schema titles.

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 opens with 'Create send between tracks,' clearly identifying the verb and resource. It distinguishes itself from siblings by explicitly referring to setup_routing for batch operations, making it clear this tool handles individual send creation.

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?

Provides explicit guidance: 'Prefer setup_routing for batch' indicates when not to use this tool. It also explains when to use MIDI parameters and references send_set_mute for muting audio, giving contextual direction for related operations.

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