catia_gsd_join

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

Annotations are all false, so the description carries the behavioral disclosure burden. It explains the combining effect and downstream purpose, but does not mention tolerance-based merging behavior, whether original elements are modified, or what the returned result is. This is adequate but not detailed.

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 concise sentences front-load the operation and then add one high-value workflow context sentence. There is no filler or repeated schema content.

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 simple tool with 4 well-described parameters and no output schema, the description covers what join does and when it fits in the workflow. Gaps like failure conditions and return value are minor for this operation, so it is nearly complete.

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 100%, so the baseline is 3; the schema already documents elements, name, geoset, and tolerance. The description adds only a small clarification that elements are surfaces or curves, not enough to raise the score.

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: 'Join several surfaces or curves into a single element', which clearly identifies the operation. It also gives workflow context by noting this precedes thickening or closing surfaces, though it does not explicitly name or differentiate against sibling alternatives like healing or fill.

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 phrase 'This is what you do before thickening or closing a set of surfaces into a solid' provides a clear when-to-use context in the surface-to-solid workflow. It does not offer exclusions or compare directly with related GSD operations.

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