Get job status

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds one behavioral detail, that the download link is only present 'if finished', which signals a conditional response, but it says nothing about rate limits, polling expectations, or how long job state is retained.

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 with zero filler; the conditional payoff (download link if finished) is packed into the same clause rather than padding.

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?

There is no output schema, so the description must carry the return-value burden, and it only partially does: it mentions status and the finished-state download link but not the possible status values, the failure case, or whether the job_id expires. Adequate for a simple lookup but leaves meaningful gaps for a polling workflow.

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?

With one parameter at 100% schema description coverage, the schema already explains that job_id comes from convert, and the description adds no further semantics such as format, expiration, or invalid-id behavior. Baseline 3 is appropriate when the schema carries the meaning.

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?

Specific verb+resource ('get the status of a conversion job') that clearly distinguishes it from siblings like convert and create_upload, and it adds what the caller actually receives (the download link). It stops short of naming a sibling or stating the lifecycle relationship to convert, so it stays at 4 rather than 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?

No when-to-use guidance appears in the description; the only hint that this follows convert lives in the schema's job_id description ('returned by convert'). There is no mention of polling, retry, or terminal-state conditions under which an agent should or should not call it.

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