draw_rectangle

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

With no annotations, the description carries full burden. It only states the rectangle is axis-aligned and DXF, but does not disclose behavior such as whether the rectangle is closed, what happens with invalid corners, permissions needed, or whether existing geometry is affected.

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 is concise with no wasted words. However, it is under-specified; a slightly longer description could convey critical parameter semantics without losing 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 4 parameters, 0% schema coverage, no annotations, and a drawing context, the description is severely incomplete. It does not cover how corner1/corner2 work, what layers/colors do, or what the output schema returns. The agent has almost no guidance beyond the tool name.

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 schema has 0% description coverage and the description adds no parameter information. While parameter names 'corner1', 'corner2' are somewhat self-explanatory, the description should explicitly connect them to the rectangle definition. No help is given for 'layer' or 'color' beyond default values.

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 verb 'draw' and resource 'rectangle' with specific qualifiers 'axis-aligned DXF', which distinguishes it from sibling tools like draw_arc or draw_circle. However, it omits that the rectangle is defined by two opposite corners (corner1, corner2) which limits clarity for an agent.

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 (e.g., draw_polyline for rotated rectangles, draw_hatch for filled rectangles). The agent must infer usage from context.

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