rhino_panelize_surface

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

No annotations beyond title; description does not disclose whether the original surface is modified or new objects are created, or what happens to the surface. It does not mention potential side effects like new objects being added to the document.

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, 11 words, no fluff. However, it lacks structure like bullet points or examples, and the brevity sacrifices completeness.

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?

Despite having an output schema, the description is too brief. It doesn't explain that panels are created as separate objects, the effect on the original surface, or how the panel type affects output geometry. For a tool with four parameters, more context is needed.

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 coverage is 100% (all four parameters have descriptions). The description adds no extra meaning beyond the schema, so baseline 3 is appropriate.

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 (subdivide a surface) and the resource (surface) with specific panel types (quad, triangle, diamond). It distinguishes from sibling tools like rhino_mesh_from_surface or rhino_uv_grid_panels.

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 use this tool vs alternatives like rhino_mesh_from_surface, rhino_panel_frames, or rhino_uv_grid_panels. No mention of prerequisites (e.g., surface must exist and be untrimmed) or when not to use.

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