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

No annotations, so the description carries the full load, and it says nothing beyond what the name implies. It does not say whether this is read-only (presumably), whether it blocks or returns immediately, whether status is eventually consistent, or how progress is expressed. The single added word 'progress' hints at a percentage but leaves the return shape undefined.

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?

One short, front-loaded sentence that gets straight to the point with no filler. It is concise, but its brevity reflects under-specification rather than tight editing.

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?

For a polling/status tool in a pipeline with competing terminals (get_result, list_for_project, cancel), an agent needs to know what statuses exist and what to do next; none of that is here, and with no annotations or output schema nothing else fills the gap.

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 0%: jobId is an undocumented string with no explanation of where it comes from (presumably render.preview/render.final) or its format. The description does not compensate, merely referring to a 'render job' without tying it to the jobId parameter.

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?

Clear verb ('Check') plus resource ('status/progress of a render job'), and the 'render.' namespace prefix ties it to render jobs. It is distinguishable from siblings like render.get_result and render.list_for_project, though the description does not explicitly contrast them.

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?

Implied usage: poll this after starting a render. No explicit statement of when to prefer render.get_result (for finished output) or render.list_for_project (for enumerating jobs), and no mention of whether it can be called on completed or failed jobs.

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