Create Ellipse

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

Discloses coordinate system (top-left origin, Y down) and bounding box semantics, but does not explain impact on existing artboard, layering, selection, or undo behavior. Annotations are present but offer minimal additional insight.

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?

Two concise sentences: first explains the tool's function, second lists parameters. No unnecessary words, front-loaded with core purpose.

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?

Explains bounding box coordinate origin and optional styling, but omits default fill/stroke behavior and units. For an 8-parameter tool without output schema, this is adequate but leaves some ambiguity about defaults.

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?

Adds context that x,y,width,height define the bounding box, complementing the schema which already describes each parameter. With 100% schema coverage, the description reinforces semantic meaning without being redundant.

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?

Clearly states 'Draw an ellipse/circle' with bounding box specification, distinguishing from other shape creation tools like illustrator_create_rectangle or illustrator_create_line.

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?

Only lists parameters without guidance on when to use this tool versus alternatives (e.g., when to draw an ellipse versus a circle or other shapes). No context on prerequisites or typical use cases.

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