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

Annotations declare destructiveHint=true and idempotentHint=false, and the description goes well beyond them: solo silences non-solo tracks, merge aborts the WHOLE move on any overlap or source transitions, delete refuses a track holding clips, and delete on an empty track usually reports removedTracks: 0 without being a failure. It also documents the invariant that video and audio counts are forced equal — the key non-obvious side effect.

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?

Front-loaded with the action list, then a numbered, well-structured section on ordering. Dense and mostly earning its space, though the 'removedTracks: 0 is not a failure' point is stated twice (in the delete bullet and again below), costing some length.

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?

No output schema exists, yet the description still discloses the key return signal (removedTracks) and the refusal behaviors. For a 12-action, 7-parameter mutation tool with destructive semantics, nothing an agent needs in order to call it correctly is missing.

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 baseline is 3, but the description ties parameters to actions: 'rename' needs name, 'merge' needs intoTrackId of the same kind, 'tidy' takes NO trackId. It also gives each action value behavioral meaning (duck uses transcript timings or energy VAD) that the bare enum list in the schema does not.

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 title-line 'Track operations on a timeline' is generic on its own, but the immediately following enumeration of the twelve actions (mute/rename/duck/merge/delete/tidy) makes the resource and scope unambiguous. An agent can distinguish this from remove_clips, manage_effects, or manage_transitions without opening the schema.

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?

Explicit routing: deleting a non-empty track is 'remove_clips, by name', track ids come from get_timeline, projectId from get_projects. It also gives an ordered procedure (merge first, then tidy once at the end) and states which action to prefer and why.

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