edit_split_delete

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

No annotations are provided, so the description carries full behavioral disclosure. It transparently states that the operation deletes audio and leaves silence, which is the key behavioral trait. It does not mention undo or other side effects, but the destructive nature is evident from 'Delete', and the silence behavior is clearly disclosed.

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 front-loads the core action ('Delete the selected audio') and immediately clarifies the distinguishing detail. There is zero fluff and every word earns its place.

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 tool with no parameters and no output schema, the description fully explains the operation's effect on the selected audio. It is complete enough for an agent to understand exactly what will happen when the tool is invoked.

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 tool has zero parameters and the schema coverage is 100% (since there are no properties). Per the baseline for 0-parameter tools, the description need not add parameter semantics, and it appropriately does not.

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 the verb 'Delete' and the resource 'the selected audio', and explicitly distinguishes the behavior by noting it does not close the gap but leaves silence. This clearly differentiates it from sibling tools like edit_delete or edit_cut, which likely close the gap.

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 the intended use case (when silence should remain after deletion) but does not explicitly name alternatives or provide when-not-to-use guidance. An agent can infer usage, but explicit routing to siblings like edit_delete is missing.

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