photoshop_select_ellipse

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

No annotations are provided, so the description carries the full burden. It discloses side effects ('replaces current selection'), preconditions ('active document; right > left and bottom > top'), and return shape. This is comprehensive for a selection tool.

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?

Tightly structured with scannable sections: purpose, use cases, return format, preconditions, and side effects. Every sentence delivers useful information with no 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?

The tool has a simple parameter set but no output schema or annotations. The description covers the return JSON, preconditions, side effects, and sibling differentiation. Nothing essential is missing 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 100%, so the baseline is 3. The description adds meaningful context beyond the schema by defining the bounding-box relationship (right > left, bottom > top) and noting the anti-aliased nature, which helps the agent validate inputs.

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 tool creates an elliptical pixel selection from a bounding box Sunday anti-aliased. It explicitly differentiates from photoshop_select_rectangle, so an agent can identify the correct tool without opening the schema.

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?

Provides explicit use cases 'circular or oval masks, vignettes, or radial edits inside a region' and an explicit exclusion 'Do NOT use when: a rectangular region is enough — use photoshop_select_rectangle.' This gives unambiguous routing guidance.

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