draw_ellipse

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

With no annotations, the description carries the full burden. It usefully discloses that the operation is wrapped in a single undo transaction, which tells the agent the draw is atomic and reversible. However, it omits which layer/frame is targeted, permission needs, and what the call returns.

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?

A single front-loaded sentence with no wasted words; the core action leads and the transactional detail trails.

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 10-parameter drawing tool with no annotations and no output schema, the description is thin. It covers purpose and atomicity but leaves layer/frame targeting and the returnPreview behavior unaddressed, which matters for correct invocation.

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 coverage is 60%, so the schema documents the bounding-box and color params while layerName, layerIndex, frameNumber, and returnPreview remain bare. The description's 'bounding box' and 'outline or filled' phrasing reinforces the x/y/width/height and filled params but adds no meaning to the undocumented targeting params.

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?

States a specific verb+resource (draws an ellipse) and adds scope detail (outline or filled, within a bounding box). It is distinguishable from siblings like draw_rectangle and draw_line by shape, though it never names them explicitly.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as draw_rectangle or flood_fill. The only contextual note is the atomic undo behavior, which is a behavioral trait rather than usage routing.

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