revolve_profile

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

With no annotations, the description carries the full burden. It discloses a key constraint (the profile must be CLOSED) and defines the axis and angle semantics. However, it does not state whether the operation produces a solid or surface, nor does it mention any prerequisites or side effects, leaving some ambiguity.

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 that communicates the operation and parameters without any fluff. Every word contributes to understanding.

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?

Since an output schema exists, return values are not needed. The description covers the core parameters and constraints, but it lacks details on the required entity type for the profile (e.g., closed polyline) and any prerequisite state. It is adequate for basic use but leaves room for more context.

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 compensates by explaining handle as '2D profile', x1/y1/x2/y2 as axis points, and angle as degrees. This adds substantial meaning beyond the bare type definitions, though it omits specifics like units or rotation direction.

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 operation: 'Revolve a CLOSED 2D profile' and specifies the axis via two points and an angle. This is a specific verb+resource construction that distinguishes it from sibling tools like extrude_profile or sweep_profile.

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 parenthetical '(turned parts)' provides clear context for when this tool is appropriate, implying rotational symmetry. However, it does not explicitly mention alternatives or exclusion criteria, so it lacks explicit 'when not to use' guidance.

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