rhino_zoom_layer

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

The description clearly states the primary behavior—zooming the active viewport—and is consistent with readOnlyHint=false. It does not disclose further behavioral details such as whether selection is preserved, whether hidden or locked objects are included, or what happens if the layer is missing or empty.

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 front-loaded sentence with no filler. Every word contributes to stating the action, target, and object scope.

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 tool with one required parameter, the description plus schema provides enough to invoke it correctly: layer path, doc_id default, active viewport, and the zoom action. It does not cover failure modes or alternative zoom tools, but an output schema exists and the operation is straightforward.

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 documents layer as 'Full layer path' and doc_id as 'Document handle id; active targets the current document.' The tool description only echoes the layer placeholder and adds no extra meaning beyond the schema, though it does not need to compensate because the schema is descriptive.

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 states an explicit verb and resource: 'Zoom the active viewport to fit every object on `layer`.' The layer-scoped object set clearly distinguishes this tool from sibling zoom operations such as rhino_zoom_extents, rhino_zoom_selected, and 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 implies the use case: fitting all objects on a given layer into the active viewport. However, it provides no explicit when-to-use guidance, no exclusions, and does not mention alternatives among the many sibling zoom tools.

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