rhino_toggle_grid

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

With no annotations provided, the description carries the full burden of explaining behavior, and it does so clearly: it flips the viewport construction grid between visible and hidden. It also implies low risk by targeting a viewport display setting rather than document geometry, though it does not mention whether the active viewport or all viewports are affected.

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?

One short sentence contains the verb, resource, and outcome with no filler or redundant information. It is front-loaded and immediately actionable.

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 display toggle, the description is complete enough to invoke correctly. The presence of an output schema covers return-value expectations, so the description needs only to state the action and target.

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 parameter semantics are not a real concern and the schema coverage is trivially 100%. The description correctly communicates that no arguments are needed by describing a simple toggle action.

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 clearly states the action ('Toggle') and the target resource ('viewport construction grid'), with the on/off effect spelled out. It is clear on its own, though it does not explicitly differentiate itself from the similarly named sibling rhino_set_grid or rhino_place_grid.

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 gives no guidance on when to use this tool versus alternatives such as rhino_set_grid or rhino_place_grid. It does not mention that this is only for the viewport grid visibility state, nor does it note when another grid-related tool would be more appropriate.

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