rhino_render_queue_submit

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

The description adds behavioral context beyond annotations: it returns a 'job_id' immediately, frames are captured on a background worker, and the backend uses '_-ViewCaptureToFile' with true photo-realistic engine on the roadmap. Annotations only indicate readOnlyHint=false and title. No contradictions.

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 description is concise, around 4 sentences, and front-loads the main purpose. However, the formatting with indentation and line breaks feels slightly informal. Every sentence adds value, with no unnecessary words.

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?

Given the tool's complexity (nested schema, background worker, polling pattern), the description covers submission, immediate return, polling, cancellation, and backend limitation. It lacks explicit mention of prerequisites (e.g., bridge setup), error handling, or the output schema (which exists but not described). An output schema is present, so return values need not be detailed, but overall completeness is adequate but not thorough.

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?

Input schema has 0% description coverage for top-level parameters per context signals. The description mentions 'frame sequence' but does not explain the nested structure (frames array) or any parameters. The schema does provide some nested property descriptions, but the description adds minimal value for parameter meaning.

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 clearly states 'Submit a frame sequence to the bridge render queue', specifying the verb (submit) and resource (frame sequence to bridge render queue). It explicitly notes 'bridge only', distinguishing it from other render tools. The mention of polling and cancellation tools further clarifies its role.

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 advises using 'rhino_render_queue_status' to poll progress and 'rhino_render_queue_cancel' to interrupt, providing explicit guidance on related tools. However, it does not explicitly state when not to use this tool or compare with direct render alternatives like 'rhino_render_to_file'.

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