catia_gsd_circle

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent creation. The description adds the intended downstream role (multi-section surface section) but says nothing about which geoset the circle lands in, whether an active geoset must be set first, or what happens on name collision.

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?

Two short sentences, no filler, with the create action and its inputs front-loaded. The second sentence is a genuinely useful orientation hint rather than padding.

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 feature-creation tool with no output schema and a moderate schema, the definition is adequate but leaves the container/target question open (geoset placement, naming), which matters given siblings like catia_gsd_set_active_geoset.

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 coverage is 75% and the schema already documents center (element name or [x,y,z] that creates a point), radius in mm, and the 'xy'/'yz'/'zx' plane options. The description only restates those three inputs, adding no syntax, units, or defaults beyond the schema.

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 verb (create) and resource (full 3D circle) along with the three inputs that define it. '3D' implicitly separates it from the sketch-level sibling catia_sketch_circle, but the description never names or contrasts that alternative explicitly.

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?

'Useful as a section for multi-sections surfaces' gives one downstream usage context, hinting when the tool is relevant. It offers no when-not guidance and does not point to catia_gsd_multi_section_surface or catia_sketch_circle as the alternative path.

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