rhino_zoom_selected

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

With no annotations provided, the description carries the full burden and does disclose the core behavior: the view is zoomed to fit the current selection. It also correctly implies a non-destructive viewport operation. It does not mention edge cases like empty selection or multi-viewport behavior, but the primary behavior is transparent.

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 concise sentence with no filler. Every word contributes meaning, and the main action is front-loaded before the target.

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 zero-parameter viewport tool with an output schema, the description is nearly complete. It defines the operation, target, and scope. The main gap is not specifying what happens when nothing is selected, but this is a minor omission given the simplicity of the tool.

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, so the schema needs no elaboration. The description adds useful semantic context by identifying the current selection as the implicit input, which is sufficient for an agent to understand how the tool operates.

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 uses a specific verb ('zoom') and resource ('currently selected objects'), making the tool's purpose immediately clear. It is naturally distinguished from siblings like rhino_zoom_extent (all objects) or rhino_zoom_layer (a layer) by explicitly scoping to the current selection.

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 phrase 'currently selected objects' implies the prerequisite that objects must be selected, but the description does not explicitly say when to use this tool versus alternatives like rhino_zoom_object, rhino_zoom_extent, or rhino_zoom_window. Usage context is implied rather than stated.

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