rhino_push_pull

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

With no annotations, the description must carry the behavioral burden, but it only states the abstract push/pull action and signed distance. It does not disclose that this is a mutating edit, that geometry is changed in place, whether it is reversible, or what input selection state is required.

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 short, front-loaded with the operation, and easy to scan. It loses a point because the Args block is inconsistent with the actual input schema, containing 'controller' while only 'distance' is exposed.

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 mutation tool with no annotations, this is incomplete: it lacks explicit selection requirements, the effect on the original solid, and any note that the operation modifies existing geometry. The output schema helps with return values, but the behavioral context is too sparse for an agent to use this safely.

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 schema provides only the integer 'distance', and the description adds key meaning: positive moves outward, negative inward. However, it also documents a 'controller' argument not present in the schema, which is potentially confusing.

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 states a specific verb ('push or pull'), a precise target ('selected sub-face of a solid'), and a quantifier ('by a given distance'). This clearly distinguishes it from generic transform tools like rhino_move and solid-edit tools like rhino_shell.

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?

No guidance is given for when to choose this tool over alternatives, nor any exclusions or workflow prerequisites. It implies a selected sub-face but does not state that a selection must be made before calling or how to prepare the model.

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