Creates circular patterns of a selected body around a specified axis, with adjustable copy count and angle spread.
Pattern a body around axis x/y/z: count copies spread over angle degrees.
| Name | Required | Description | Default |
|---|---|---|---|
| axis | No | z | |
| body | Yes | ||
| angle | No | ||
| count | Yes |
Changes observed during successful MCP inspections.
v0.6.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Description adds that it creates copies over an angle, which aligns with non-destructive hints, but doesn't provide additional behavioral context beyond what annotations already indicate.
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?
Single sentence with key verb, resource, and parameters, no redundant information, highly efficient.
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?
Covers core functionality and main parameters, but could mention default values for axis and angle for completeness, though not critical given the description.
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?
Despite 0% schema coverage, description explains axis options (x/y/z), that count is copies, and angle is in degrees, adding significant meaning beyond schema titles.
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?
Description clearly states 'Pattern a body around axis x/y/z' with specific verb and resource, and distinguishes from siblings like fusion_rectangular_pattern by the circular nature.
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?
Implies usage for circular patterns but lacks explicit guidance on when to use versus alternatives like fusion_rectangular_pattern, and no exclusion criteria.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.