edit_delete

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

No annotations are provided, so the description carries the behavioral disclosure burden. It goes beyond the bare name by stating the clipboard behavior and the selection prerequisite. Still, it does not disclose whether the deletion is undoable or whether any project/undo context is affected, which would be relevant for a destructive edit 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?

Two short sentences deliver the action, a key behavioral distinction, and the prerequisite with no filler. The main verb and resource are front-loaded in the first sentence.

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 edit command with no output schema, the description contains the essential information: what is deleted, that clipboard contents are not changed, and that a region selection is required. It leaves some safety context (undo behavior) implicit, but nothing required to invoke the tool correctly is missing.

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 and 100% schema description coverage, so there are no parameter details the description must add. Per the zero-parameter baseline, the description is adequate without explaining parameter semantics.

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 and resource: 'Delete the selected audio.' It also distinguishes itself from sibling copy/cut tools by explicitly stating 'does not copy to clipboard,' so an agent can tell edit_delete apart from edit_cut and edit_copy even without examining their 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?

The description gives a clear precondition: 'Select a region first.' It also implies when this tool is appropriate rather than cut/copy by noting that it does not copy to clipboard. However, it does not explicitly name alternatives or state when to prefer a sibling like edit_split_delete or edit_cut.

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