edit_image

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

No annotations provided so description must fully disclose behavior. Mentions editing but does not explain whether original file is overwritten, what happens on failure, or any other side effects.

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?

Efficient single sentence with bullet-like examples. Clear and front-loaded, but could be slightly more structured (e.g., separate actions from uses).

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?

Description covers what the tool does but omits output specification (e.g., where edited image is saved) and behavioral details. Missing completeness for a mutation tool with no output schema.

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% with clear parameter descriptions. Description adds little beyond listing capabilities, providing no extra semantic detail for parameters.

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?

Description clearly states action (edit), resource (existing image file), and lists specific capabilities (add/remove elements, change styles, style transfer). Distinguishes from siblings like compose_images and generate_image.

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 explicit guidance on when to use this tool vs siblings. Lacks context like prerequisites (e.g., image must exist) or when to prefer continue_editing.

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