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

No annotations are provided, so the description carries the full burden. It does disclose the key behavioral trait — the call fails if items exist unless deleteItems=true — and that a cascade delete of child items occurs. It omits other relevant behavior: irreversibility, required permissions, and side effects on the parent edit.

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?

Two tight sentences, zero filler, with the core action front-loaded and the failure condition placed immediately after the parameter that controls it.

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 destructive call with no output schema and three schema-documented required IDs, the description covers the critical trap an agent must avoid (silent failure vs. cascade deletion). It stops short of warning that this delete is destructive and likely irreversible, which would be valuable given no annotations.

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 goes beyond the schema by explaining the consequence of deleteItems (failure when omitted, cascade deletion when set), which the schema's one-line description does not convey. Required IDs remain schema-documented only.

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?

States a precise verb+resource ("Delete an overlay track") with no ambiguity, and the resource name distinguishes it from nearby siblings such as delete_overlay_item, delete_audio_track, and delete_transition. An agent can identify the operation 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?

The description gives genuine conditional guidance for invoking it: set deleteItems=true to remove items too, otherwise the call fails. However, it offers no guidance on when to choose this tool over alternatives (e.g., delete_overlay_item for individual items, or update_overlay_track), so usage is implied rather than fully routed.

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