rhino_zoom_layer

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

Description truthfully describes the action and its effect on the viewport. Annotations only have readOnlyHint: false, which is consistent with changing the view. No hidden side effects or behavioral details beyond the stated purpose are needed for this simple operation.

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?

Single sentence of 10 words, front-loaded with action and resource. No redundancy or unnecessary text.

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?

Description is sufficient for a simple zoom tool. It specifies the viewport and the layer scope. Schema covers parameter details, and output schema exists. Minor missing information: behavior when layer has no objects or does not exist, but not critical for agent usage.

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?

Description does not mention parameters. Input schema provides descriptions for both parameters (layer: 'Full layer path.', doc_id: 'Document handle id; active targets the current document'). Schema covers parameter meaning, so baseline 3 is appropriate.

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?

Description clearly states action (zoom), resource (active viewport), and scope (fit every object on a given layer). It distinguishes itself from sibling tools like rhino_zoom_extent and rhino_zoom_object by specifying layer-based zooming.

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?

No guidance on when to use this tool versus alternatives. Does not mention when to prefer this over rhino_zoom_extent or rhino_zoom_object, nor any prerequisites or limitations.

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