draw_polygon

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

With no annotations, the description should disclose behavioral traits. It mentions drawing on a specific layer/frame and optional fill/color, but fails to specify coordinate system, blending behavior, or whether drawing overwrites existing pixels. This is insufficient for safe invocation.

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 concise, covering all parameters in a single block without superfluous text. It is front-loaded with the purpose, but lacks structural aids like bullet points for readability.

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?

For a 7-parameter tool with many sibling drawing tools, the description misses key context: no return value description, no mention of side effects, and no explanation of polygon closure or point ordering. It feels incomplete for an agent to use correctly.

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 description adds meaning beyond the schema by listing parameter types, defaults, and brief explanations. However, it leaves ambiguity for 'points' (key names not specified) and 'color' (format not described). Given 0% schema coverage, it partially compensates but is incomplete.

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 action (draw) and resource (polygon) on a specific layer/frame. It differentiates from sibling tools like draw_circle or draw_line by the shape type, though it could be more precise about the polygon being closed and defined by points.

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_line or draw_rectangle. The description does not mention scenarios or prerequisites, leaving the agent to infer usage context.

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