ass_align_to_silence

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

No annotations are provided, so the description carries the full burden, and it does the most important part: it loudly declares 'never modifies the document' and marks the return with applied:False plus a note. It also discloses that max_shift_ms filters suggestions and the shift_only semantics. It stops short of permissions/rate-limit context, so a 4 rather than 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?

Front-loaded with purpose and cleanly sectioned into Args/Returns with no filler sentences. Slightly redundant in that an output schema already exists yet the full return shape is restated, which costs a bit of brevity.

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 7-param, all-optional tool with no annotations, the description covers the read-only guarantee, every parameter's meaning, and the return contract. Nothing an agent needs to invoke it correctly is missing.

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 0% (no parameter descriptions), so the description must compensate, and it documents all 7 params. It adds real meaning beyond the schema: noise_db is passed to silencedetect, shift_only 'both'/'start' controls whether the end moves, and max_shift_ms filters out long suggestions.

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?

States a specific verb and resource ('Report audio silence intervals and the per-line shifts they suggest') and explicitly distinguishes itself from its write counterpart, ass_align_lines_to_silence. An agent can tell exactly what this does and how it differs from the applying tool.

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?

Names the alternative and the condition that selects it: this tool is the 'look before it leaps' preview, while ass_align_lines_to_silence applies the same plan when dry_run=False. Explicit when-to-use routing against a sibling.

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