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

Annotations already mark destructiveHint=true and readOnlyHint=false, so the mutation nature is clear. The description adds valuable concurrency details (element-scoped vs whole-project mutation) and references the music_id source ('returned by add_audio'). While it doesn't discuss reversibility or error states, the concurrency guidance is a meaningful addition beyond annotations.

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 well-structured with a brief introductory sentence followed by a bulleted list for target modes and a separate concurrency section. It is concise at ~100 words and front-loads the core purpose. The only minor issue is that the concurrency section could be slightly more compact, but overall it earns its space.

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 tool's moderate complexity (two modes, conditional parameters) and no output schema, the description covers the essential use cases, parameter dependencies, and concurrency behavior. It could be improved by noting what happens on success (e.g., returns confirmation or updated project state) and error conditions (e.g., invalid element_id), but it is largely complete for an AI agent to use correctly.

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 100%, so the baseline is 3. The description adds value by clarifying the target-dependent parameter requirements (e.g., 'requires music_id — returned by add_audio') and explaining the relationship between target and conditional parameters, but the schema already describes each parameter's purpose adequately.

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 the tool removes an element or audio track from a project, specifying two distinct targets ('element' and 'audio') with their required parameters. This distinguishes it from sibling tools like 'remove_clip' (which removes entire clips) and 'remove_elements' (which likely removes multiple elements at once).

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 explicitly explains when to use each target mode ('target=element' vs 'target=audio'), including the required parameters for each (clip_index+element_id vs music_id). It also provides concurrency guidance, telling the agent to serialize 'target=audio' mutations on the same project while noting element-scoped operations are parallel-safe with other element edits.

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