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

No annotations are provided, so the description carries the full burden, and it does so well: it discloses the state machine (Pending → Processing → Completed/Failed), that Failed carries a reason, the recommended polling cadence, and that the response includes the full conversion object with the converted file uid. It does not mention auth requirements, job expiry, or behavior for an unknown job_id, so it falls short of exhaustive.

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 tight sentences: identity, state lifecycle, then operational guidance, all front-loaded with no filler. Every sentence earns its place by covering purpose, states, and next action.

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 compensates by explaining what is returned (status, failure reason, full conversion object with converted file uid). Combined with the polling cadence and the follow-up call, an agent has everything needed to poll and branch on the result.

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 100% and there is a single required parameter whose schema description already states it is the conversion uid. The description reinforces the provenance of the id (returned by convert_file), adding slight value but nothing beyond the schema's own text.

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 ('Returns the current status of a conversion job') and enumerates the exact states, which distinguishes it from siblings like convert_file or start_conversion that initiate work. An agent can identify this as the status-polling tool without opening the schema.

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 when to call it ('Poll every 2–3 seconds after convert_file / start_conversion') and what to do next ('when Completed, call get_download_url'). This names both the triggering siblings and the follow-up sibling, leaving nothing to inference.

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