rhino_render_viewport

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

Description mentions 'bridge required' and 'render' but does not disclose side effects, performance implications, or prerequisites beyond the bridge. Annotations only provide readOnlyHint=false, which is consistent but incomplete.

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 concise sentence that front-loads key information. No wasted words, though it omits some details.

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 nested input schema with 4 parameters and an output schema, the description is too minimal. It does not explain output format, resolution defaults, or error conditions when bridge is absent.

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?

No parameter details in description. Schema has some description on 'doc_id' but schema coverage is 0% per context. Description adds no value beyond the 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?

Description clearly states action 'render', target 'active viewport', and output 'image file'. The '(bridge required)' adds a constraint. It distinguishes from some siblings like 'rhino_screenshot' but not from 'rhino_render_to_file'.

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?

No usage guidelines provided. Does not specify when to use this tool versus alternatives like 'rhino_viewport_image' or 'rhino_render_to_file'. Implies usage for rendering to file but lacks context.

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