delete_clip

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

The description adds meaningful behavior beyond the destructiveHint annotation by revealing the two-phase plan-or-delete workflow and narrowing the destructive action to one exact occupied Session clip. This gives an agent useful context about preflight planning before a destructive call.

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 front-loaded sentence with no filler or redundant restating of the tool name. Every word contributes to the core meaning.

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 rich parameter schema and destructive annotations, the description is mostly sufficient. The main gap is that it does not explicitly explain the plan-confirm-delete confirmation flow or output semantics, though the schema's dryRun, planHash, and confirmationToken fields cover most of that burden.

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 parameters are already well-documented. The description adds no direct parameter-level detail, but its 'plan' and 'exact' wording loosely aligns with dryRun and expectedStateVersion without expanding on them.

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 gives a specific operation ('Plan or delete') and a precise resource ('one exact occupied Session clip'). It clearly differentiates from the sibling delete_arrangement_clip by identifying the target as a Session clip.

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 resource type implies when to use this tool versus arrangement-clip tools, but the description does not explicitly name alternatives or state when-not-to-use conditions. Usage context is implied rather than directly guided.

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