rhino_1view

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

With no annotations, the description carries the full behavioral burden. It clearly states that the operation maximizes the active viewport and is view-related rather than a model-editing action. It does not mention whether the action toggles back to a multi-viewport layout, but for a simple no-argument viewport command this is a minor gap.

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, focused sentence that front-loads the action and then specifies the target and result. There is no filler, redundancy, or repetition of schema information.

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 parameterless viewport command with an output schema present, the description provides the essential info an agent needs to invoke it correctly. It is only missing a brief statement about when to choose this over rhino_3view or rhino_4view, so it is strong but not maximal.

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 and an empty input schema, so there is no parameter meaning for the description to add. The baseline 4 applies here because no parameter documentation is required.

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 concrete verb ('Maximize') with an identifiable resource ('active viewport') and a clear outcome ('fill the entire viewport area'). It is unambiguous, though it does not explicitly contrast itself with siblings like rhino_3view or rhino_4view, so differentiation relies on name and context.

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 intended use is reasonably implied: use it when the active viewport should be enlarged to fill the screen. However, there is no explicit when-to-use guidance, no mention of alternatives, and no exclusions, leaving the agent to infer selection among the many viewport-related tools.

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