rhino_extend_surface

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

There are no annotations, so the description carries the full burden. It discloses interactive selection and a dict result, but does not state whether the operation modifies the existing surface, requires an open document, or what happens if no valid edge is selected.

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 and front-loaded with the core purpose. It contains no unnecessary prose, though the Args/Returns section is somewhat minimal.

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?

With no annotations and a 0% schema coverage, the description leaves out important operational details such as distance units, prerequisites, whether the surface is modified in place, and error behavior when interactive selection fails. The output schema likely covers the return structure, but overall context is incomplete.

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%, so the description must compensate. 'Distance: Extension distance' adds only marginal meaning beyond the schema field name and does not specify units, sign behavior, or allowed range. The mentioned controller argument is also absent from the schema.

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 and resource: extend a surface edge by a given distance. It also clarifies that the edge is selected interactively, which distinguishes it from curve-extension tools like rhino_extend_curve.

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 clearly conveys when to use this tool: when a surface edge needs to be extended by a numeric distance. The note that the edge is selected interactively gives useful contextual guidance, though it does not explicitly name alternatives or exclusion conditions.

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