add_rectangle

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

Describes that four line segments are automatically generated, forming a closed rectangle suitable for extrusion. However, lacks details about sketch activation requirements or error conditions. No annotations provided, so description carries burden but offers some useful behavioral context.

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 paragraphs with key information front-loaded. No unnecessary filler.

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?

Lacks explicit mention of sketch activation requirement. Output schema exists, so return value documentation is not needed, but parameter aliases could be better explained.

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 baseline is 3. Description adds little beyond schema; does not clarify the alias parameter groups (x1,y1 vs corner1_x,corner1_y) or when to use each.

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 the tool adds a rectangle to the current sketch, specifying it creates a closed profile from two opposite corner points. It distinguishes from sibling sketch tools like add_line or add_circle.

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 on when to use this tool over alternatives like add_polygon or add_centerline. No prerequisites or exclusions mentioned.

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