get_audio_channel_mapping

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

No annotations are provided, so the description carries the full behavioral burden. It states only that it fetches a mapping, without explaining the return shape (for example an array of channel indices), what happens for items with no audio, or whether this requires an open project. For a zero-annotation tool, this is a large omission.

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?

A single, front-loaded sentence with no filler. It is efficient, though its brevity leaves several important points unstated.

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 one-parameter getter with no output schema and no annotations, the description is barely sufficient. It is missing the return format for the mapping and any prerequisite context, such as whether the project item must be audio-bearing.

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?

There is a single parameter, nodeId, and the schema already documents it at 100% coverage. The description adds no extra meaning, such as whether the nodeId can refer to a bin or sequence rather than a clip. With high schema coverage, baseline 3 is appropriate.

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 names a specific verb and resource: 'Get the audio channel mapping of a project item'. An agent can distinguish it from the write counterpart set_audio_channel_mapping by the get/set contrast. However, no explicit sibling differentiation is stated in the text itself.

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?

There is no guidance on when to call this tool instead of alternatives, and no mention of when it is not appropriate. The presence of set_audio_channel_mapping and other project-item getters in the sibling list makes the absence of routing guidance a real gap, though the getter name implies reading only.

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