rhino_render_queue_status

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

The description adds detail about what the status includes (progress, completed frames), which goes beyond the readOnlyHint and idempotentHint annotations. No contradictions or undisclosed behavioral traits.

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?

A single, clear sentence that efficiently conveys the tool's purpose with no wasted 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?

The description, combined with annotations and output schema, provides sufficient context for a simple inspect operation. It covers key aspects (status, progress, frames) without over-explaining.

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?

The single parameter (job_id) is described in the schema as 'GUID returned by rhino_render_queue_submit,' but the tool description itself adds no additional meaning or context for parameters.

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 it inspects a queued render job's status, progress, and completed frames. However, it does not differentiate from sibling tool rhino_render_queue_list which might also show status for multiple jobs.

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 provides no explicit guidance on when to use this tool versus alternatives like rhino_render_queue_list or rhino_render_queue_cancel. Usage is implied but not clarified.

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