edit_silence

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

No annotations provided, so description carries full burden. While 'replace' implies mutation, the description fails to disclose destructiveness, whether the operation affects clip length, if it's reversible via undo, or how it interacts with the cursor/selection state post-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?

Single efficient sentence with zero redundancy. Information is front-loaded and every word serves a purpose.

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 covers the core action but omits critical context like selection requirements (though implied) and behavioral side effects. Adequate but minimal for an audio editing operation.

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?

Input schema has zero parameters, triggering the baseline score of 4 per evaluation rules. The description implies reliance on a pre-existing selection ('selected audio'), which provides necessary context for the empty parameter list.

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 states a specific verb (replace), resource (selected audio), and result (silence). It clearly distinguishes from siblings like edit_delete (removal without preserving duration), edit_cut (clipboard operation), and truncate_silence (removes silence vs. creating 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?

No explicit guidance on when to use this versus edit_delete (which likely removes audio entirely) or truncate_silence (which removes silence rather than creating it). No mention of prerequisites like requiring an active selection.

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