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

Adds key context beyond annotations: it's free, returns status and result, and requires polling until 'done'. Annotations already declare readOnly/idempotent, so the description's polling guidance is the real added value. Could mention error states.

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?

Three short sentences, front-loaded with cost, purpose, and action. No wasted words, though 'Poll until done is true' could be tightened.

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?

Given the existence of an output schema, the description needn't explain return values. It covers cost, relationship to sibling, and polling behavior – everything needed for an agent to call it correctly.

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% and one required parameter exists (jobId), but the description doesn't define it. Baseline 3 is appropriate since schema structure alone doesn't add semantic meaning, though the parameter itself is self-explanatory from name.

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 (status/result) and resource (job created by speech-to-text_v1), and clearly distinguishes itself from the sibling speech-to-text_v1 by referencing it as the creator.

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?

Explicitly says 'Poll until done is true,' telling the agent exactly when and how to use this tool relative to the synchronous sibling.

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