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

Annotations already flag destructive=true and idempotent=false, so the safety profile is covered. The description still adds real behavioral content: it discloses that edits ripple (shifting downstream clip timing) and that a small margin is preserved so speech never clips, which explains why output differs from a naive cut. It does not mention undo or transcript dependency, keeping it short of a 5.

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?

Two compact sentences: the core mechanic and effect first, then the tuning presets. Every clause carries information; nothing repeats the schema or annotations.

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?

Five required params are all documented in-schema, annotations cover the destructive/non-idempotent profile, and no output schema exists. The description supplies the operational semantics needed to call it correctly; only the implicit transcript prerequisite and the fact that timing shifts downstream are left partly unstated.

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?

Schema coverage is 100%, so the baseline is 3. The description earns above baseline by giving minGapSec concrete operating points (0.6 tight, 1.0 balanced, 1.5 loose), turning a bare number into an actionable tuning scale that the schema does not provide.

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 gives a specific verb and resource (cuts silent gaps inside a clip) and explains the mechanism precisely: pauses longer than minGapSec become a ripple delete. That mechanism implicitly separates it from remove_words and ripple_delete_ranges, but neither sibling is named, so an agent must infer the boundary.

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?

Usage is implied by 'between transcribed words' and the recommended minGapSec presets (0.6 tight / 1.0 balanced / 1.5 loose), which is genuinely helpful tuning guidance. However there is no explicit statement of when to pick this over remove_words or ripple_delete_ranges, and no prerequisite such as run start_transcription first.

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