rhino_zoom_extent

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

Annotations indicate readOnlyHint=false (modifies view), and the description confirms it changes the active view. It adds context about the scope (selected or all objects) beyond what annotations provide, though it could mention potential side effects like resetting the view.

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 sentence with 10 words, front-loaded with the main action and resource. No fluff or redundancy; every word contributes to understanding.

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 view zoom tool, the description covers the core function adequately. It does not need to explain return values (output schema exists). However, it could mention that it works on the active viewport only, but the current wording is clear enough.

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 input schema already provides clear descriptions for both parameters (doc_id and object_ids), so the description does not add new meaning. Despite 0% description coverage (as reported), the schema itself is rich, warranting a baseline of 3.

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 action ('Zoom'), the resource ('active view'), and the scope ('selected (or all) objects'). It effectively distinguishes from sibling tools like rhino_zoom_object and rhino_zoom_layer by specifying the extent of all selected or all 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 implies usage when the goal is to zoom to the extent of selected or all objects, but it does not provide explicit guidance on when to use this tool over siblings (e.g., rhino_zoom_object for specific objects) or when not to use it.

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