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

Goes well beyond the annotations by explaining why readOnlyHint=false: checking can persist the completed model and restart failed work on another provider. It also discloses the polling loop and the intermediate return ('updated timing'), which the annotations cannot convey. No contradiction with the declared openWorldHint/idempotentHint=false.

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?

The polling guidance is front-loaded and useful, but the final sentence almost verbatim repeats the opening sentence, wasting space. The middle clause about saving and restarting is dense and could be split for scanability.

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 carries the burden of describing returns and does so: updated timing while pending, inline rendering in the 3D viewer when done, and the suggestion to call again. Nothing needed to invoke it correctly is missing.

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%, so both job_id and the nested refine object are already fully documented, including the 'pass it back unchanged' caveat. The description only restates that job_id comes from the pending result and says nothing about refine, so the baseline 3 applies.

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 and resource: check a pending 3D generation and collect the finished model. The scope (only jobs that returned "pending") is explicit. It does not, however, distinguish itself from the sibling get_job, which an agent will reasonably confuse with this polling tool.

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?

Gives a clear trigger condition: 'Use this when a generation tool returned status "pending" and you need to collect the finished model', plus the polling cadence ('call again after the suggested wait'). No explicit exclusion versus get_job or get_item_source, so it stops short of full routing guidance.

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