thicken_surfaceConvert a surface body into a solid by adding thickness. Specify body, thickness in cm, and direction (positive, negative, or symmetric) for precise control.
Thicken a surface body into a solid
| Name | Required | Description | Default |
|---|---|---|---|
| body_name | Yes | ||
| direction | No | symmetric | |
| thickness | Yes | Thickness (cm) |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations indicate this is a non-read-only, non-idempotent, non-destructive operation, which the description aligns with by implying a creation action ('into a solid'). However, the description adds minimal behavioral context beyond annotations—it doesn't specify if the operation modifies the original surface or creates a new body, or any error conditions like invalid inputs.
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, direct sentence with no wasted words, making it highly concise and front-loaded. It efficiently communicates the core action without unnecessary elaboration.
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?
Given the complexity of a 3D modeling operation with 3 parameters, low schema coverage (33%), no output schema, and annotations that only cover basic hints, the description is inadequate. It lacks details on input validation, output format, error handling, or how it integrates with sibling tools, leaving significant gaps for an AI agent.
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 33% (only 'thickness' has a description), and the description does not compensate by explaining parameters like 'body_name' or 'direction'. It implies 'thickness' but doesn't add meaning beyond the schema's numeric constraint and unit. With low coverage, the description falls short of fully clarifying parameter roles.
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 ('Thicken') and the target ('a surface body into a solid'), making the purpose immediately understandable. However, it does not explicitly differentiate this tool from other modeling operations like 'extrude' or 'shell', which could also create solids from surfaces, leaving room for sibling confusion.
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 like 'extrude' or 'shell', nor does it mention prerequisites such as needing an existing surface body. It simply states what the tool does without contextual usage information.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.