rhino_zoom_object

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

The description clearly communicates the main behavior: the active viewport's view changes to fit the specified objects. It does not dwell on side effects because this is a view-state change, not a destructive operation. A minor gap is that it does not clarify whether the active viewport belongs to the document referenced by the optional doc_id, which could slightly confuse agents using a non-active document handle.

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 short, front-loaded sentence with no filler. The verb, target, scope, and criterion are all present, and every word contributes to understanding the tool's purpose.

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 one-required-parameter zoom operation with an output schema, this description is nearly complete. It covers the key intent and scope, but it stops short of explaining the exact object_id semantics and how the optional doc_id affects the 'active viewport' wording.

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 schema provides no description for object_ids (0% coverage), and the tool description only restates 'given object ids' without explaining what those IDs are, where they come from, or whether they must correspond to valid objects in the target document. The doc_id parameter is documented in the schema, but object_ids semantics are not meaningfully enriched by the description.

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 names a specific verb and resource: zooming the active viewport to fit provided object IDs. It also distinguishes itself from sibling zoom tools like rhino_zoom_extent, rhino_zoom_selected, and rhino_zoom_window by focusing on explicit object IDs rather than all objects, current selection, or a 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 gives clear context: use this when you have object IDs and want the active viewport framed exactly to those objects. It does not explicitly name alternatives or exclusion cases, but the 'given object ids' qualifier makes the intended use evident among the many zoom-related siblings.

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