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

Annotations already mark this as a safe, idempotent, read-only polling operation, so the bar is lower. The description adds useful behavioral detail beyond the annotations: the exact status values (queued | rendering | completed | failed) and that outputUrl is only populated when status is 'completed'.

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 compact sentences with no filler. The action is front-loaded ('Poll a render job by id'), followed by the single most important output condition and an explicit status enum.

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?

Complete for a simple one-parameter polling tool. The description covers the input, the status lifecycle, and the key output field, while annotations handle safety and idempotency. No output schema exists, but the description provides enough return-value context.

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 the id parameter already includes the essential provenance ('from neuron_studio_render / neuron_studio_make'). The description adds no new parameter-level detail beyond confirming that the id identifies a render job, 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?

The description states a specific action (poll a render job by id) and identifies the finished MP4 output condition, making the tool's purpose unambiguous. It does not explicitly distinguish itself from sibling status tools like neuron_studio_generate_video_status or neuron_studio_transform_video_status, though the 'render job' terminology plus the id provenance in the schema narrow it down.

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?

The description clearly implies when to use it: after submitting a render job, poll this tool by id to monitor progress. It does not explicitly state when not to use it or name the alternative status tools, but the schema's id description anchors it to neuron_studio_render / neuron_studio_make.

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