rhino_soft_edit_surface

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

No annotations or description details: it does not state whether the surface is modified in place, whether it affects control points, what falloff/strength values are used, or if undo is supported. With no annotations, this ambiguity is significant.

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 sentence, no filler, direct statement of operation and object.

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?

Basic operation is clear, but no information about expected result, output, or interaction with selection. Since an output schema exists but is not included, and the description omits side effects, completeness is moderate.

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 declared parameters, so the baseline is high. The description at least clarifies that it targets the currently selected surface, but gives no detail on any optional editing parameters that might exist.

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 verb 'Apply' plus object 'soft editing' to 'selected surface' clearly identifies a deformation operation. It also differentiates from sibling rhino_soft_edit_curve by targeting surfaces.

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 on when to choose this over related deform tools such as rhino_smooth, rhino_cage_edit, or rhino_bend. The phrase 'selected surface' implies a precondition but does not explain how to set up or verify the selection.

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