create_slot

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

No annotations provided, so description carries full burden. It discloses the slot geometry, the parametric constraint (non-driving dimensions), and the active sketch requirement. It does not mention return value or side effects like sketch closure, but the major behavioral trait (non-parametric) is well covered.

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 verbose, including bilingual text (Spanish and English) which adds redundancy. While the content is valuable, it could be more concise. The key information is front-loaded, but the Spanish repetition detracts from conciseness.

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?

Given 5 required parameters, no output schema, and no annotations, the description covers geometry, parameter semantics, usage context, and a critical behavioral caveat (non-parametric dimensions). It lacks error conditions or return value, but these are partially expected without output schema. Overall adequate.

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 0%, so description must explain parameters. It does so with a docstring-like list: x1_mm, y1_mm, x2_mm, y2_mm as center-line endpoints and width_mm as slot width. This adds meaning beyond the bare schema titles and compensates for lack of parameter descriptions.

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 'Draw a straight slot on the active sketch' and explains the geometry (rounded-rectangle with semicircular end-caps). It distinguishes this tool from sibling sketch tools like create_rectangle or create_circle by specifying the slot shape and common autoparts use.

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 description provides a concrete usage example (adjustable bolt slots) and explicit caveats: requires active sketch and the parametric limitation that modify_dimension cannot resize width/endpoints. It doesn't explicitly contrast with alternatives but implies specialized slot creation.

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