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. It correctly identifies the destructive nature of the operation ('delete'), but lacks crucial details such as undoability, whether the operation requires an existing selection to function, or side effects on the project state.

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 efficient sentence with a clarifying parenthetical. Every word earns its place: 'Trim audio outside the selection' defines the operation, and the parenthetical removes ambiguity without adding fluff.

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?

While the core operation is described, the description omits critical contextual information given the lack of annotations and output schema: specifically, that a selection must exist beforehand (prerequisite) and what happens if invoked without one. For a destructive editing tool, this gap is significant.

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, establishing a baseline score of 4. The description adequately compensates by explaining the implicit input (the current selection) that the tool operates upon, though no additional parameter-level semantics are needed.

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 provides a specific verb ('Trim'), resource ('audio'), and scope ('outside the selection'), with the parenthetical '(delete everything except selected region)' clearly distinguishing this tool from siblings like edit_delete or edit_cut which operate on the selection itself rather than preserving 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 provides no explicit guidance on when to use this tool versus alternatives (e.g., when to use edit_trim vs edit_delete or edit_cut), nor does it mention prerequisites such as requiring an active selection before invocation.

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