Poll a render job

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

No annotations are provided, so the description carries the burden, and it does disclose the status enumeration, that progress and downloadUrl vary by lifecycle stage, and that results may already be complete inline. It stops short of stating polling cadence, job expiry, or failure detail, which would matter for an async poller.

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 sentences, front-loaded with the return shape and then the gating condition. Every clause earns its place, including the explicit 'you do NOT need to poll' guard.

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?

No output schema exists, and the description compensates by enumerating the return fields. Combined with the clear preconditions, an agent has everything needed to decide whether and how to call this 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?

One parameter with 0% schema description coverage, but the description supplies the semantics the schema lacks: the jobId originates from render_screenshots on the keyed/async path. The schema itself carries the UUID pattern. Slightly thin on what a malformed or expired jobId yields.

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 (poll/returns status) and resource (render job), and enumerates the exact return values (queued|running|done|failed, progress, downloadUrl). It is immediately distinguishable from render_screenshots, the only sibling.

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 states the triggering condition: use only when render_screenshots returned a jobId with status=queued, and explicitly states when NOT to use it (if a downloadUrl was already returned). Both the positive and negative cases are named.

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