voicememos_compare_readers

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

With no annotations present, the description carries the full burden and does disclose the key side effect: it writes a Markdown report (with a listening checklist) and returns only a summary. That non-obvious write-then-summarize behavior is exactly what an agent needs. It does not say where the report file lands or whether it overwrites prior reports.

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 summary sentence followed by a compact Args block that maps one-to-one to the parameters. No filler; the only structural quibble is that the report-writing behavior sits in the second line rather than being grouped with the summary.

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?

No output schema exists, and the description does state the return surface ('returns the summary') plus the artifact produced, which is the critical gap covered. Remaining omissions—report output path and handling of the samples cap—are modest for a zero-required-parameter reporting tool.

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%, so the description must compensate, and it largely does: it defines 'since'/'until' as inclusive date bounds in YYYY-MM-DD and 'samples' as disagreements to sample per language with a max of 50. It omits the schema's default of 15 for samples and doesn't clarify what happens if since > until or if the max is exceeded (clamped vs. error).

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?

Opens with a specific verb+resource: 'Compare primary engine and second reader per language', and enumerates the comparison dimensions (agreement, calibration, samples). This clearly distinguishes it from siblings like voicememos_second_read (which presumably produces one reading) and voicememos_transcribe, though it never names those siblings explicitly.

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 only implied by the phrasing 'compare primary engine and second reader', suggesting it is run after a second read exists. There is no explicit statement of when to use it, when not to, or which sibling to call first to populate the second reader.

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