rhino_render_queue_submit

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

Beyond the readOnlyHint=false annotation, the description discloses asynchronous behavior, background-worker execution, the concrete capture mechanism (_ViewCaptureToFile), and the v0.5 backend limitation. This adds meaningful behavioral context without contradicting the annotations.

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 compact sentences with the core purpose front-loaded, follow-up tools named explicitly, and the backend limitation as a brief closing note. There is no filler, repetition, or unnecessary detail.

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?

Covers the success path (immediate job_id), the asynchronous lifecycle (status and cancel companions), and the current rendering limitation. Since an output schema exists and the input schema describes frame details, nothing essential is missing for an agent to call this tool correctly.

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?

With schema description coverage at 0%, the description should compensate by helping agents understand frame fields, but it only says 'frame sequence' at a high level. It adds no parameter-level detail about view, width/height defaults, output_path requirements, or the frames array limits, leaving agents to rely entirely on the nested schema.

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 action ('Submit'), a precise resource ('a frame sequence to the bridge render queue'), and explicitly scopes itself ('bridge only'). It is clearly distinguishable from sibling render and queue tools like rhino_render_queue_status, rhino_render_queue_cancel, and rhino_render_viewport.

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 describes the expected workflow: returns job_id immediately, frames are captured on a background worker, use rhino_render_queue_status to poll, and rhino_render_queue_cancel to interrupt. It also sets clear expectations by noting the current backend only captures viewport frames and true photo-realistic rendering is not yet available.

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