draw_ellipse

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

With no annotations provided, the description carries the full burden of explaining behavior, yet it only says 'draw an ellipse on the canvas.' It does not disclose whether the ellipse is filled by default, how the `filled` parameter interacts, whether existing pixels are overwritten, or how frame/layer parameters are resolved. This is minimal behavioral context.

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 a single, front-loaded sentence with no wasted words. It efficiently states the tool's core purpose without restating schema fields or adding filler.

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 the 8-parameter input schema, nested color object, no annotations, and no output schema, this one-line description is severely incomplete. It lacks coordinate system details, defaults for `filled`, layer/frame behavior, and any mention of the return value or side effects. The description is inadequate for an agent to use this tool 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?

Schema description coverage is only 13%, with only `color` described as '{r,g,b,a}'. The description adds no meaning to required parameters like `x`, `y`, `width`, `height`, or optional parameters like `frame`, `layer`, and `filled`. It also doesn't clarify whether x/y are center-based or corner-based, leaving essential semantics unspecified.

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 uses a specific verb 'Draw' and a clear resource 'ellipse on the canvas,' which distinguishes it from related sibling tools such as draw_circle, draw_rect, and draw_line. It immediately and unambiguously states the tool's function.

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?

The description implies that this tool should be used when an ellipse is needed, but it provides no explicit guidance on when to choose it over the many other drawing tools, nor does it mention any exclusions or alternative tools. The usage context is only barely implied by the tool name and description.

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