rhino_blend_surface_edges

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

The description does not mention any side effects, permissions, or destructive actions. It only states what it creates, so the agent has no information about whether it modifies existing objects or requires special access.

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, concise sentence that directly conveys the purpose without unnecessary words. It is well-structured and easy to parse.

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 is brief and lacks important context for a complex geometric operation. It doesn't explain the expected inputs, output type, or how continuity is controlled, making it insufficient for an agent to fully understand the tool's requirements.

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 description does not elaborate on the parameters beyond the schema. It mentions 'continuity control' but doesn't explain the continuity parameter's meaning or the edge IDs. The schema provides some description for edge IDs but not for continuity, and the tool description adds no extra detail.

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 tool creates a blend surface between two edges with continuity control, using a specific verb 'Create' and specifying the resource and key feature. It distinguishes from other surface tools by mentioning 'two surface edges' and 'continuity control'.

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 use case but does not explicitly mention when to use this tool over alternatives like other blend or surface tools. There is no guidance on prerequisites 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.