Create Rectangle

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

Annotations indicate non-read-only and non-idempotent. Description adds that it creates a closed rectangular polyline, which is consistent. No additional behavioral details are provided, but annotations cover safety basics, making this adequate.

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 sentences, front-loaded with the core purpose, no wasted words. Structurally optimal for quick understanding.

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 presence of output schema, full schema coverage, and annotations, the description sufficiently covers the tool's role. Could mention that it creates a polyline entity specifically, but 'closed rectangular polyline' implies that. Nearly complete for a simple creation tool.

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% with clear parameter descriptions. Description adds the concept of 'two corner points,' which aligns with x1,y1 and x2,y2 but does not further clarify formats or constraints. Baseline 3 is appropriate.

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 the tool creates a closed rectangular polyline from two corner points. Distinguish from sibling entity_create_polyline by specifying 'rectangular' and noting it's a convenience wrapper.

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?

Identifies as a convenience wrapper around entity_create_polyline, implying use for rectangles. Lacks explicit when-not-to-use or alternatives beyond polyline, but sufficient for a simple tool.

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