edit_delete

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

No annotations are present, so the description carries the behavioral burden. It discloses the destructive action, the gap-closing behavior, the fact that nothing is copied to the clipboard, and the required selection state. It does not mention undo, but the core behavior is clearly and accurately conveyed.

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 sentences, front-loaded with the action and its behavioral consequence. Every phrase adds information and there is no filler.

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 zero-parameter command with no output schema, the description covers the command's effect, its non-effect on the clipboard, and the required user state. There are no significant gaps an agent would need to resolve before calling it.

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?

The input schema has zero parameters, so the baseline is 4. The description still adds useful meaning by explaining that the operation applies to the current selection rather than any explicit argument.

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 ('Delete') and resource ('selected audio'), and adds the consequence 'closing the gap' plus the explicit contrast 'does not copy to clipboard.' This clearly distinguishes it from sibling tools like edit_cut without needing to inspect schemas.

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?

It gives a concrete precondition: 'Select tracks and a time range first,' which tells an agent how to prepare a valid invocation. It does not explicitly name alternatives or when-not conditions, but the clipboard note implies when edit_cut or edit_copy would be more appropriate.

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