catia_create_sketch

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

Annotations only declare it is a non-idempotent mutation with no global side effects; the description adds real behavior the agent needs: the sketch lands in the active body, it is opened for editing, an offset plane is inserted into the tree, and axis orientation is defined relative to the support.

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?

Front-loaded with the action and the support-selection priority before the axis-alignment detail. Dense but every clause carries information; the axis-mapping sentence is the most expendable but is still useful orientation context.

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 zero-required-param mutation tool with no output schema, the description covers creation, support resolution, editing state, tree effects, and the closing step. Nothing an agent needs to invoke it correctly is missing.

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, but the description adds genuine meaning: what face_point really selects ('the top face of the boss'), that plane is auto-detected from the face normal and can be omitted, and how the sketch axes map to the chosen origin plane.

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 and resource ('Create a new 2D sketch ... and open it for editing'), scopes it to the active body, and distinguishes itself from the many catia_sketch_* geometry siblings that add content rather than create the sketch container itself.

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?

Gives an explicit priority order for support selection (face_point, else plane + offset, else origin plane) and names the follow-up tool (catia_close_sketch). The agent knows both how to choose a support and how to end the workflow.

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