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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds meaningful context beyond them: 'Public access' discloses the auth requirement and 'completion or failure reason' describes the returned content. It omits rate limits or polling guidance, but the added auth/return context is genuine.

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?

Two short sentences that front-load the verb and resource, with no redundant restatement of the name. 'Public access.' is terse and functional rather than filler, though it sits as a fragment at the end.

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 single-param read tool with no output schema, the description should carry the return semantics, and it does name completion/failure as the payload. It leaves gaps: no description of status values, not-found behavior, or the job_id itself, which are meaningful for a status-polling 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 description coverage is 0% and the sole parameter job_id is never mentioned in the description, so nothing compensates for the documentation gap. The field name is fairly self-explanatory, which prevents a 1, but the description adds no meaning about format, source, or validity of the id.

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 ('Read') and resource ('a documentary job's completion or failure reason'), and even states what the return conveys. It stops short of differentiating itself from similar status siblings like get_submission_status, so an agent cannot fully disambiguate from the name alone.

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?

'before taking the next action' implies the tool is a status-check step in a workflow, and 'Public access' signals no auth is required. However, no alternative tool is named and no explicit when-not-to-use condition is given, so the routing guidance is only implied.

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