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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description contributes that the response includes progress and an ETA, which is genuine added context, but it says nothing about job state values, terminal states, or error/not-found behavior for a tool with no output schema.

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 tight sentence with the core purpose front-loaded and no filler. Every clause earns its place by adding either the resource or the returned data.

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 one-parameter read-only lookup with full annotations, the definition covers purpose and return highlights adequately. It could be stronger by noting that the job id comes from create_script_audio_job or by hinting at terminal states, but nothing critical is missing to invoke 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?

There is a single parameter with 100% schema description coverage including a UUID pattern, so the schema does the work here. The description adds no meaning about the id beyond what the schema already states, which matches the baseline for full coverage.

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 gives a specific verb and resource ("Get one Script to audio job") and adds the payload highlights (progress, estimated seconds remaining). The word "one" implicitly separates it from list_script_audio_jobs, but no sibling is named 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?

Mentioning progress and remaining time implies a status-polling use case, but the description never states when to call this versus list_script_audio_jobs or create_script_audio_job, nor any preconditions. Usage must be inferred from the name and the return contents.

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