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

With readOnlyHint already present, the description still adds useful behavioral context: it is project-scoped, deterministic, capped at 60 seconds, reads each kept span across cuts, and flags cuts inside words with the sound-safe edge. It is consistent with the annotations and adds substantial value, though it remains somewhat opaque about exact output shape.

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 front-loads scope and purpose, and most clauses carry relevant information. However, it is a dense run-on with nested parentheticals and jargon, making it harder to parse than necessary for an agent selecting and invoking the tool.

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?

It covers scope, max window length, output content, and cross-cut behavior well enough for a complex read tool with no output schema. The unresolved required-versus-omittable start/end conflict and the lack of exact time units or output shape leave an important gap.

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 only 33%, with project_id documented but start and end left as bare numbers. The description adds meaning by calling start/end a program-clock window capped at 60 seconds, but it also says they can be omitted to read the whole short while the schema marks both as required, creating a direct invocation conflict.

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 read operation: deterministic listening over a program window that surfaces transcript words, untranscribed sounds, clipping, and clicks. It also distinguishes the tool from related siblings such as keep_segments and critique_short, though the phrasing is dense rather than immediately plain.

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?

It gives clear usage context: 'use it before and after a cut' and 'Omit start/end to read the whole short.' It does not explicitly state when not to use the tool or fully compare it against alternatives, so it stops short of the top score.

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