edit_trim

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

With no annotations provided, the description carries the full burden of behavioral disclosure. The parenthetical 'delete everything except selected region' explicitly communicates the destructive effect, leaving no ambiguity that this tool removes audio. It could add more context about prerequisites such as requiring an active selection, but the core behavior is transparent.

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 one tight, front-loaded sentence. The parenthetical adds immediate clarity without redundancy or filler. 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 zero-parameter tool with no output schema, the description is nearly complete: it states the operation and its result. It only omits an explicit mention that a selection must already exist, but this is strongly implied by the wording and the tool name.

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 there are no parameter semantics to document. The standalone baseline for zero-parameter tools applies, and the description does not need to compensate for any schema gaps.

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 ('Trim') and resource ('audio outside the selection') and clarifies the exact behavior in parentheses: 'delete everything except selected region.' This clearly distinguishes it from sibling tools like edit_cut or edit_delete, which target the selected region rather than everything outside it.

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 clearly implies when to use the tool: when a selection exists and the user wants to keep only that selected region while discarding all other audio. It does not explicitly name alternatives or exclusions, but the behavior is specific enough that an agent can infer the correct usage context.

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