add_audio

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

Without annotations, the description carries the full burden. It only implies mutation (adding to timeline) but does not disclose effects on the FCPXML, requirements, side effects, or how the tool handles existing assets or conflicts.

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 conveys the core purpose with no fluff. It is appropriately concise for the tool's function.

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 9 parameters, no output schema, and no annotations, the description is insufficient. It lacks explanation of critical distinctions (e.g., when to use asset_id vs src, how role and lane affect placement) and does not cover return behavior.

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?

All 9 parameters have descriptions in the schema (100% coverage), so baseline is 3. The tool description does not add additional meaning beyond the schema; it omits details like how parent_clip_id distinguishes clip attachment vs music bed, which is a key semantic choice.

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 clearly states 'Add an audio clip or music bed to the timeline', specifying the action (add) and resource (audio clip/music bed) and target (timeline). It distinguishes from sibling tools like add_connected_clip (which may add connected clips) and insert_clip (which inserts rather than adds).

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. The description does not mention prerequisites or scenarios where this tool is preferred over siblings like add_connected_clip or insert_clip.

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