send_set_pan

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Set send pan' but does not explain what happens if the send does not exist, whether the operation is reversible, or any side effects on existing settings. This lack of detail is critical 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?

While very short (one sentence plus an Args list), the description is under-specified for a tool with three required parameters. Conciseness should not come at the cost of clarity; here it omits essential context about the tool's purpose and behavior.

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?

Given the lack of annotations, output schema, and the presence of three required parameters, the description is incomplete. It does not explain what a 'send' is in this audio production context, how track_index and send_index relate, or what the pan value does acoustically. This leaves the agent guessing about the tool's role.

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 must add meaning. The 'Args' section barely improves on the schema: 'track_index: Source track' and 'send_index: Send index' are tautologies. Only 'pan: -1.0 to 1.0' adds value by specifying the range. The description does not explain what these parameters mean in context (e.g., track indexing, send creation order).

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 'Set send pan' states a specific verb and resource, but it essentially repeats the tool name without adding context. Among siblings like send_create and send_remove, it distinguishes itself only by name, not by clarifying what a 'send pan' is or how it differs from other send modifications.

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 on when to use this tool versus alternatives (e.g., send_set_volume or send_set_mute). There is no mention of prerequisites, such as the send needing to exist first, or typical use cases like balancing stereo sends.

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