rhino_set_view

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only restates the core action and parameter meaning; it does not disclose that this alters view state rather than model geometry, whether targeting a viewport makes it active, whether new viewports are created, or whether the operation persists. These gaps matter for a state-changing tool with zero annotation coverage.

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 compact: one purpose sentence followed by a minimal Args block. The first sentence is appropriately front-loaded, and the Args block earns its place by supplying enum values the schema lacks. The docstring formatting adds slight verbosity but no waste.

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 two-parameter tool with an output schema, the description covers the core operation and both parameters. But it leaves ambiguity about the interaction between 'active viewport' and 'viewport to target' (does targeting switch the active viewport?), and it fails to disambiguate from the similarly named sibling rhino_view_set. These are clear gaps an agent would hit when selecting and invoking 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?

Schema description coverage is 0%, so the description must compensate, and it does. It enumerates the exact valid values for view_name (Top, Front, Right, Perspective, Back, Left, Bottom, Isometric) — information absent from the schema, which has no enums — and clarifies that viewport is optional. This adds real meaning beyond the bare string types.

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 opens with a specific verb+resource: 'Set the active viewport to a standard view.' This clearly identifies the action and scope. However, it does not differentiate from the sibling tool 'rhino_view_set', which appears to describe the same operation, so it falls short of full sibling distinction.

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 no when-to-use guidance, exclusions, or references to alternatives. Given the enormous sibling list containing view-related tools such as rhino_zoom_extent, rhino_named_views, rhino_named_view_save, and the near-duplicate rhino_view_set, an agent receives no help choosing among them.

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