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

Annotations already declare destructiveHint=true, readOnlyHint=false, openWorldHint=false and idempotentHint=false, so the description's added value is its disclosure of asynchronous job semantics ('Returns immediately with a task ID'), the worker dependency, and the accepted input form. It does not explain why the operation is flagged destructive or whether re-queuing duplicates work, which would have closed the last gap.

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?

Four short declarative sentences, front-loaded with the action and measurements, then preconditions, then the polling alternative. No filler and nothing repeated from the schema or annotations.

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 an output schema present, return values need not be described, and the description covers async behavior, prerequisites, input restrictions, and the follow-up tool. Only the meaning of task_id remains under-specified relative to a one-parameter, zero-coverage schema.

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 one parameter and the schema description coverage is 0%, so the description must carry the burden. It implies the identifier refers to a previously uploaded render and rules out local paths and third-party URLs, but it never states that task_id is the handle returned by create_render_upload, nor its format or length constraints.

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 opens with a specific verb+resource pairing ('Queue measurements for your successfully uploaded render') and enumerates exactly what is measured: cuts, OCR, motion, audio, synchronization. It is clearly distinguishable from sibling tools create_render_upload (upload) and get_render_result (retrieve results).

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?

It states preconditions ('successfully uploaded render', 'Requires a running worker'), the alternative for obtaining output ('poll get_render_result for real measured results'), and an explicit exclusion ('No local path or third-party video URL is accepted'). An agent knows both when to call this and when not to.

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