rhino_clipping_plane

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

Annotations only mark readOnlyHint=false; the description productively adds that the operation creates a plane and applies it to all viewports. It doesn't discuss naming/layering or effects on existing clipping planes, but this is a minor gap for a creation 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, front-loaded, and free of filler. Every word adds meaningful information about the operation and its scope.

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 creation tool with a rich nested schema and an output schema, the description captures the essential scope (all viewports) and the mutating nature. It doesn't address the sibling overlap, but nothing critical is missing for 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% and the description offers no parameter-level detail; the agent must rely entirely on the nested schema for origin/axis semantics. The word 'clipping plane' loosely connects to the plane argument but adds no specific meaning.

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 states a specific verb ('Add'), a concrete resource ('clipping plane'), and a clear scope ('all viewports'). It is unambiguous on its own, but it does not explicitly distinguish this from the sibling rhino_add_clipping_plane.

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 'all viewports' scope provides implicit context for when this tool is appropriate, but there is no explicit guidance about alternatives, exclusions, or when not to use it.

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