rhino_zoom_extent

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

The description doesn't disclose any side effects beyond the obvious view change, and the annotation readOnlyHint=false already indicates it modifies the view state. It adds little extra behavioral context, such as how object visibility or layer state might influence the zoom result.

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, unambiguous sentence that conveys the essential action and optional scope without any fluff. It is well-structured 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 view-zoom command, the description fully covers the action, target view, and the optional object restriction. No further context is necessary for a user to understand or invoke the tool correctly.

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 phrase 'selected (or all)' loosely corresponds to the object_ids parameter, but the schema already provides descriptive comments for doc_id and object_ids. The description does not add meaningful detail beyond what the schema already specifies, so it does not elevate the parameter understanding.

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 tool's purpose: zooming the active view to the extent of selected or all objects. It uses a specific verb ('Zoom') and resource ('active view'), but does not explicitly differentiate it from sibling view-zoom tools like rhino_zoom_object or rhino_zoom_window.

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 some usage context by indicating that zooming can be restricted to selected objects via object_ids, otherwise it targets all visible objects. However, it does not reference alternative tools or provide guidance on when to choose this tool over others.

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