rhino_create_mesh

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

All annotations are false, so the description carries the full burden of behavioral disclosure. It states that it creates a mesh, which implies a mutation side effect, but does not disclose what happens with invalid indices, whether the mesh object is added to the Rhino scene, or any validation behavior. Minimal but adequate for a straightforward creation operation.

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?

A single sentence that front-loads the action and input types with zero filler. The description is appropriately compact and immediately scannable, making it easy for an agent to grasp the core function.

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 simple creation tool with thorough schema descriptions and an existing output schema, the description is sufficient. It need not explain return values (output schema exists) or enumerate edge cases since the schema covers formats. The only missing element is usage alternatives, which is already penalized under usage_guidelines.

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 mentions 'vertices and face indices', which aligns with the two required parameters, but adds no detail beyond what the schema already provides. The schema includes comprehensive descriptions for vertices, faces, and optional fields, including format hints. With schema description coverage at 0% (no parameter specifics in the description), it fails to compensate, though the schema covers all needed semantics.

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 'Create' and the resource 'mesh', specifying inputs as 'vertices and face indices' and explicitly noting 'triangles or quads'. This distinguishes it from sibling creation tools like rhino_create_sphere or rhino_create_box, which target different geometry types.

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 provides no guidance on when to use this tool versus alternatives such as rhino_create_surface_from_points or rhino_create_patch. It does not mention exclusions, prerequisites, or related mesh tools like rhino_check_mesh. The agent must infer usage from the name and context alone.

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