rhino_offset_surface

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

Annotations already indicate readOnlyHint=false, so the write nature is known. The description adds that offsetting occurs along the normal, but lacks details on side effects (e.g., whether original surface is modified), authorization needs, or performance implications.

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, clear sentence with no wasted words. It is appropriately sized for a straightforward operation.

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?

The description covers the core operation but omits contextual details such as whether the tool returns a new surface ID (output schema exists but not described). Given the tool's moderate complexity and presence of an output schema, more completeness would be beneficial.

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?

With 0% schema description coverage, the description must compensate for parameter meanings. It only explains the 'distance' parameter, leaving surface_id, tolerance, name, layer, and doc_id completely unexplained. This is insufficient for an agent to correctly use all parameters.

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 (offset), the object (surface), and the key parameter (distance). It distinguishes this tool from other surface operations like extrude or revolve by specifying the unique operation of offsetting along the normal.

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 implies the usage scenario (creating an offset surface) but does not explicitly state when to use this tool versus alternatives, nor does it mention any prerequisites or exclusions. The agent must infer the context from the tool name and siblings.

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