catia_gsd_helix

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

Annotations provide no safety hints (all false), so the description must carry the burden. It only states creation and does not disclose preconditions (e.g., required existing axis/start point tokens), side effects on the part, or return 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?

One concise sentence, front-loaded with action and object, no wasted words. The structure is ideal for quick scanning.

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?

With 8 parameters, no output schema, and no annotations easing the burden, the description is too sparse to fully guide usage; it lacks details on prerequisites, behavior when inputs are invalid, and what the result is (e.g., a new feature).

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?

All parameters are fully described in the schema with high coverage, so the description adds no extra parameter semantics; it only gives general context about springs/threads. Baseline score is appropriate since schema carries the details.

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 ('helix around an axis'), and even gives a use-case ('for a spring or a thread'), which differentiates it from other GSD creation tools like sweep or extrude. The description is precise and unambiguous.

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?

Implies usage for helixes but does not contrast with alternatives such as catia_thread or catia_gsd_sweep. No explicit when-to-use vs other tools, and no exclusions, leaving the agent to infer from context.

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