delete_clip

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

The description states 'Delete' which aligns with the destructiveHint annotation. However, it adds no additional behavioral context (e.g., irreversibility, effect on playback) beyond what the annotation already provides.

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 is front-loaded and contains zero wasted words.

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 has two required parameters and no descriptions, the description is insufficient. It does not define what a clip slot is or how to interpret the indices. The presence of an output schema is not detailed, and the description fails to compensate for the lack of parameter metadata.

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 0% with no parameter descriptions in the input schema. The tool description does not explain the parameters (track_index, clip_index) at all, leaving the agent to infer meaning from names alone.

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 it deletes a Session-view clip from a clip slot. This distinguishes it from siblings like delete_arrangement_clip (arrangement view) and delete_track, providing specific verb+resource.

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 on when to use this tool versus alternatives (e.g., delete_arrangement_clip for arrangement clips) or any prerequisites. The description is minimal.

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