draw_square

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

No annotations are provided, so the description must disclose behavioral traits. It mentions 'draw' but does not clarify what this entails (e.g., TCP movement, path planning, state changes). No side effects, safety concerns, or required robot modes are described.

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 concise but includes an erroneous reference to 'circle' in the coordinate explanation, which reduces clarity. It is front-loaded with the main action but could be more focused.

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 lack of output schema and annotations, the description should comprehensively cover behavior. It fails to explain what 'draw' means concretely, does not specify coordinate system or units beyond meters for border, and omits error handling or constraints. The missing 'ip' parameter is a significant gap.

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 fully explain parameters. It explains 'origin' as TCP start position, 'border' as side length, and 'coordinate' as plane orientation, but the 'ip' parameter is entirely undocumented. Also, 'origin' is an array with no further detail.

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 'draw a square' with origin and side length, and mentions horizontal/vertical direction and coordinate plane, which clarifies the basic purpose. However, it confusingly refers to 'circle' in the coordinate parameter description, and does not explain the 'ip' parameter, causing ambiguity.

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 explicit guidance on when to use this tool versus alternatives like draw_circle or draw_rectangle. The context is implied by the tool name and sibling tools, but no when-not-to-use or prerequisite conditions are provided.

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