rhino_zoom_object

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

Annotations indicate readOnlyHint: false, so description carries some burden. It discloses the tool zooms the active viewport to fit objects exactly, which implies a view modification. Beyond annotations, it adds the 'exactly fitting' detail but does not discuss side effects, permission needs, or error conditions.

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 a single, concise sentence with no wasted words. It front-loads the essential action and target efficiently.

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?

For a simple zoom-to-objects tool, the description covers the core functionality. It could mention error handling or that object_ids must exist, but given the tool's simplicity and the presence of an output schema, it is largely complete.

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 description coverage is 0%, so description must compensate. The description only mentions 'given object ids' without explaining the format, the doc_id parameter (default 'active'), or constraints like max 500 items. The schema itself has minimal descriptions, leaving the agent with gaps.

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 the verb 'Zoom', the resource 'active viewport', and the target 'given object ids exactly'. It is specific about the action and distinguishes from siblings like rhino_zoom_extent or rhino_zoom_layer by focusing on specific objects.

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 says to zoom to object ids but does not provide explicit guidance on when to use this tool vs alternatives like rhino_zoom_extent or rhino_zoom_layer. There is no mention of prerequisites or exclusions, relying on the tool name and sibling context.

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