Generates a torus solid for CAD drawings from major and minor radii, with optional center position, unit, and layer.
Create a torus solid.
| Name | Required | Description | Default |
|---|---|---|---|
| cx | No | ||
| cy | No | ||
| cz | No | ||
| unit | No | ||
| layer | No | ||
| majorRadius | Yes | ||
| minorRadius | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full behavioral burden. It says the result is a solid, but does not disclose side effects, required coordinate system, layer behavior, units, or whether the entity is immediately added to the model.
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 front-loaded sentence with no wasted words. However, it is too terse to be considered appropriately sized for a 7-parameter solid creation tool.
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 no annotations, no output schema, 7 parameters, and 0% schema description coverage, the description is incomplete. It omits essential details about parameters, units, placement, and layer assignment needed to invoke the tool correctly.
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 0% and the description adds no parameter meaning. It does not explain majorRadius, minorRadius, the optional center coordinates, unit, or layer, leaving all 7 parameters undocumented semantically.
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 states a specific verb and resource: "Create a torus solid." It clearly identifies the primitive being created, though it does not explicitly differentiate from siblings like create_sphere or create_cylinder beyond the tool name itself.
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 create_box, create_sphere, or create_cylinder. It simply states the operation without context, exclusions, or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.