delete_clip

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

Annotations already declare destructiveHint=true, so the safety profile is covered. The description adds valuable behavioral context: it specifies that the tool deletes Session or arrangement clips and instructs the agent to confirm with the user before deleting their own material. It does not mention undo or whether deletion is reversible, but this is a strong addition over the 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?

Two short, front-loaded sentences with no wasted words. The purpose is stated first, followed by the destructive confirmation requirement.

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?

The annotations cover destructiveness and no output schema exists, so return values need not be explained. However, for a tool with three parameters at 0% schema coverage and two deletion modes (Session vs arrangement), the description is too thin to fully guide correct invocation, especially regarding which parameters select which mode.

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% for all three parameters (slot, track, arrangement_clip). The description mentions 'Session or arrangement clip,' which hints at two modes, but it does not explain what slot, track, or arrangement_clip mean or how they map to the modes. It fails to compensate for the undocumented schema.

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 states a specific verb (Delete) and resource (Session or arrangement clip), clearly distinguishing it from sibling deletion tools for scenes, tracks, notes, devices, and locators. An agent can identify exactly what this tool removes 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 implies usage by saying it deletes a Session or arrangement clip, and it adds a caution about confirming with the user before deleting their own material. However, it does not name alternatives or state when-not to use this tool versus delete_scene, delete_track, or clear_arrangement.

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