geometry_add_rectangle

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

Describes only the action of adding a rectangle without disclosing behavioral traits like side effects, dependency on geometry existence, or performance implications. No annotations exist to compensate.

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?

Concise docstring format with Args and Returns sections. The first sentence clearly states purpose. Every sentence serves a purpose, though the Returns section is minimal.

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 the basics for a simple add tool but lacks details on return value format and prerequisites like needing an open geometry or work plane. Output schema is absent, so description carries additional burden.

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?

Provides brief descriptions for each parameter (e.g., 'position: Base position [x, y] in meters') and default values, adding some meaning beyond the schema. However, with 0% schema coverage, more detail would be beneficial.

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 rectangle to a 2D geometry or work plane' with specific verb and resource, distinguishing it from siblings like geometry_add_block or geometry_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 vs alternatives (e.g., circle, block). Does not specify prerequisites or context such as requiring an existing geometry.

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