add_sketch_constraint

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

With no annotations, the description must convey behavioral traits. It states the action but omits side effects (e.g., model rebuild), success/failure conditions, or the requirement for an active sketch. The tool modifies sketch state, but this is not disclosed.

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 single-sentence description is concise but under-specified. It front-loads the core action but omits important details, making it minimally adequate.

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 the tool's complexity (4 parameters, 12 constraint types, no output schema), the description is incomplete. It does not explain return values, state changes, or usage context, leaving critical gaps for an agent.

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?

The input schema covers 100% of parameter descriptions, so the baseline is 3. The description adds no value beyond the schema; it does not mention parameters or provide additional context for their use.

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 'Add constraints between sketch entities' uses a specific verb and resource, clearly identifying the tool's action. It distinguishes from siblings like 'add_sketch_dimension' by focusing on constraints rather than dimensions. However, it lacks mention of the variety of constraint types, which are detailed in the schema.

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 guidance is provided on when to use this tool versus alternatives like 'edit_sketch' or 'add_sketch_dimension'. There is no mention of prerequisites (e.g., an active sketch) or context for when constraint addition is appropriate.

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