add_cylinder

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

No annotations are present, so the description carries the burden. It discloses that the tool returns mass properties including the volume formula, and hints at state requirements with 'Use new_part first.' However, it does not describe side effects on the current part, placement/axis orientation, or failure behavior.

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?

Three short sentences, purpose first, no filler. 'The first revolve-based primitive' adds positioning context but is somewhat vague; overall it is 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?

For a creation tool with no annotations and no output schema, it leaves important gaps: default axis/orientation, units, placement, and behavior when no part exists. It covers purpose, prerequisite, and return value, but not enough for confident invocation.

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%, so the description must compensate, but it only gives a volume formula using r while the schema parameter is diameter_mm. It does not explain diameter_mm, height_mm, or the optional name parameter beyond their names.

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?

States a specific action ('Create a cylinder by revolving a profile 360° about an axis') with the resource and construction method. It is clear, though it does not explicitly differentiate from sibling add_revolved_profile beyond calling itself 'the first revolve-based primitive.'

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?

Provides a prerequisite ('Use new_part first') and implies it is the primitive form of revolve, but does not state when to choose it over add_revolved_profile or other primitives like add_disc/add_cone. No exclusions or alternative conditions are given.

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