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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered structurally. The description adds that results carry status and audio URLs and that this avoids re-paying for synthesis, which is real behavioral value, but says nothing about pagination/ordering (how 'recent' is defined) with a limit capped at 50.

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?

A single front-loaded sentence that combines the action, the returned data, and the motivating benefit with no filler or redundancy.

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?

With no output schema, the description usefully previews the return payload (status, audio URLs), and annotations cover safety. However, an agent still lacks any explanation of limit semantics or the job_type enum, which are needed to call the tool confidently, leaving it only minimally complete.

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 description coverage is 0%, so the description carries the full burden for both parameters, yet it never mentions 'limit' or 'job_type'. The enum values single/multi/srt are especially opaque and left unexplained, so the description does not compensate for the coverage gap.

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+resource (list recent speech jobs) and even names the payload fields returned (status, audio URLs), which is more than a restatement of the title. It does not explicitly differentiate itself from the similar-sounding siblings get_job_detail and get_job_status, so it stops short of a 5.

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?

The trailing clause 'to reuse earlier audio instead of paying again' supplies a genuine usage motivation, but there is no explicit when-to-use/when-not guidance and no named alternative (e.g. get_job_detail for a single job). Usage is implied rather than instructed.

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