fusion_sketch_constrain

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

Annotations already indicate mutation and non-idempotency. Description adds that for coincident/midpoint, entity_one is a sketch-point index, but does not discuss conflict behavior or the open-world hint implications.

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 efficient sentences: first defines purpose and lists types, second adds specific parameter detail and value proposition. No waste.

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?

Covers main action and constraint types, but omits explanation of optional parameters and does not state that the tool operates on an existing sketch. Given complexity, more detail would help.

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?

With 0% schema coverage, description only explains 'type' and partially 'entity_one' (for coincident/midpoint). Fails to explain 'entity_two' and 'symmetry_line', leaving significant gaps.

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?

Clearly states 'Add a geometric constraint between sketch entities' with specific verb and resource. Lists all constraint types and distinguishes from other sketch creation/modification sibling tools.

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?

No explicit guidance on when to use vs alternatives (e.g., when to use coincident vs tangent). Only a vague value statement about parametric sketches, but no when-not-to-use or comparison with other tools.

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