mcp_opendaw_set_send_pan

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It simply says 'Set' and gives the value range, but does not mention side effects, non-reversibility, whether the send must already exist, or any error behavior. This is minimal for a mutation tool.

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 compact and front-loaded: one purpose sentence followed by a concise parameter list. Every line adds value and there is no filler or 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?

The description covers the essential parameters and the pan scale, but for a mutating tool with no annotations, it lacks usage context, prerequisites, and error handling details. The operation is simple and the parameter documentation is solid, so it is minimally complete but has clear gaps.

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%, but the description manually documents all three parameters: unit_index, send_index, and pan. It also explains pan semantics with a full left/center/full right mapping, fully compensating for the schema's lack of descriptions.

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 a specific verb+resource: 'Set the stereo pan for an aux send.' It also defines the allowable range (-1.0 to 1.0), making the action immediately clear. This differentiates it from sibling send tools like set_send_level and set_send_routing.

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 is provided about when to use this tool versus alternatives such as set_track_panning or set_send_level. There is no mention of prerequisites like an existing send or how invalid indices/pan values are handled. The usage context is only implied by the tool name and parameter descriptions.

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