set_project_item_audio_channel_mapping

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

The description only states the mapping action and API used. It does not disclose behavior like range validation, reversibility, or side effects. With annotations providing only false flags (readOnlyHint=false, destructiveHint=false), the description carries the transparency burden but fails to add meaningful context.

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 a single sentence that clearly states the purpose. It is concise and front-loaded, but could be slightly more structured (e.g., listing key behavior) without becoming verbose.

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 an output schema and the tool's mutation nature, the description should explain return values or effects on the project. It provides no such information, leaving an agent without enough context to anticipate the tool's full impact.

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 100%, so the description adds little beyond the parameter definitions. The terms 'output channel' and 'source channel' align with the schema but do not clarify concepts like zero-based indexing or valid ranges.

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 uses a specific verb 'Map' and identifies the resource ('output audio channel of a project item to a source channel'). It also references the documented API, making the action clear and distinct from sibling tools, none of which handle audio channel mapping.

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?

The description provides no guidance on when to use this tool versus alternatives like adjust_audio_levels or apply_audio_effect. It does not mention prerequisites, limitations, or when not to use it.

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