truncate_silence

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

No annotations are provided, so the description carries full burden. It describes parameters but lacks details on whether the operation is destructive, how the selection is affected, or undo behavior. The phrase 'in the selected audio' provides some context but is insufficient.

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 brief (one sentence plus a list) and structured. The list is clear and easy to parse. The initial sentence could be more precise, but overall it is efficient.

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?

Given 5 parameters and no output schema or annotations, the description covers parameters well but omits important behavioral context (e.g., if it modifies the track or selection, prerequisites, undoability). It is adequate but not complete.

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 Args section adds meaningful explanations beyond the schema names and defaults, including units (dB, seconds) and action-specific behavior (compress_percent only for Compress). However, the action parameter's two options are not explained.

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 tool truncates or compresses silence in selected audio, with a practical use case (removing dead air). It is specific but does not explicitly differentiate from related sibling tools like edit_silence.

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 suggests when to use it (removing dead air) but offers no guidance on when not to use it or alternatives. The action parameter is introduced without context on choosing between Truncate and Compress.

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