live12_clip_delete

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Deletes' signals a mutation, but there is no mention of irreversibility, required permissions, side effects, or error behavior when the slot is empty—significant gaps for a destructive operation.

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 sentence with the core action front-loaded and no wasted words. The API reference in parentheses is compact and useful for developers.

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 simple two-parameter delete tool with full schema coverage and no output schema, the description states the essential action adequately. However, given it is a destructive operation with no annotations, it should do more to warn about irreversibility and edge cases.

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%, with clear zero-based descriptions for both track_index and slot_index. The description adds no meaning beyond the schema, so the baseline of 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 uses a specific verb (deletes) and target (the clip occupying a Session view slot), and the parenthetical (ClipSlot.delete_clip) ties it to the Live API. This clearly distinguishes it from siblings like live12_clip_remove_notes, which removes notes within a clip rather than deleting the clip 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?

The description implies when to use the tool—removing a clip from a session slot—but does not state any explicit when/when-not conditions or alternatives. It also omits prerequisites such as whether the slot must contain a clip or what happens if it is empty.

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