draw_rectangle

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

No annotations are provided, so the description carries the full burden. It mentions drawing in 'horizontal or vertical direction' but fails to disclose side effects, return values, or error conditions. The coordinate parameter description is garbled with circle-related text, undermining transparency.

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 description is relatively short but includes irrelevant text about circles and inconsistent terminology (square vs rectangle). It could be more organized and error-free.

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 no annotations, no output schema, and 5 parameters (4 required), the description should cover behavior, return values, and error handling. It only explains input parameters incompletely, with no mention of output or execution guarantees.

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 description coverage is 0%, so the description must compensate. It explains origin as TCP start, width and height as lengths in meters, and coordinate with a default and plane orientation, though the coordinate description is erroneous (mentions circle). The ip parameter is not explained, but overall some value is added beyond the schema names.

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 states the tool draws a shape using origin, width, and height, but mistakenly calls it a square instead of a rectangle, causing confusion with the sibling tool draw_square. The verb 'draw' and object 'rectangle' from the name are clear, but the description's inconsistency reduces clarity.

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 versus alternatives like draw_square or draw_circle. Only parameter descriptions are provided, with no mention of prerequisites or context for usage.

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