rhino_zoom_extents

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

Annotations already declare idempotentHint=true, destructiveHint=false, and readOnlyHint=false, indicating a safe, repeatable action. The description adds the specific behavior of adjusting the viewport camera. It does not contradict annotations, and it provides the essential behavior without unnecessary detail.

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, direct sentence that fully states the purpose. There is no filler or redundant information. The essential idea is front-loaded and immediately understandable.

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, zero-parameter, idempotent action, the description is complete. It specifies the active viewport and the result. One could argue for mentioning that it does not alter objects or selection, but the idempotentHint already covers safety. The existence of an output schema (likely void) further reduces the need to describe return values.

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 tool has zero parameters and the schema is empty (100% coverage). The description does not need to add parameter semantics. Per the rubric, baseline for 0 params is 4, and there is no missing information.

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 ('the active viewport'), and the result ('show the entire scene'). This is specific enough to distinguish from view-related siblings like rhino_set_view or rhino_capture_view, which serve different purposes.

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?

There is no explicit guidance on when to use this tool versus alternatives. However, it is a self-contained viewport adjustment with no obvious competing tool, so the absence of explicit exclusions is acceptable. The context implies it is used when the user wants to see the whole scene.

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