Edit Image

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

Annotations already indicate read-only and non-destructive behavior. The description adds valuable context: editor transforms are persistent and user-facing, while resource template transforms are ephemeral and LLM-facing. This clarifies the tool's role without contradicting annotations.

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 sentences, front-loaded with the core purpose. The second sentence efficiently distinguishes this tool from resource templates. No filler or redundancy.

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 simple tool with strong annotations and full schema coverage, the description is mostly complete. However, it does not clarify the return behavior after opening the editor or explicitly state that the original image is preserved when saving a new image, leaving slight ambiguity.

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?

The schema fully documents image_id (100% coverage), so the baseline is 3. The description adds the useful point that edits apply to the original image, not a resource template, helping the AI understand the parameter's meaning beyond the schema.

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 states a specific verb+resource: 'Open an image for interactive editing' and includes concrete operations (crop, rotate, flip). It clearly distinguishes this from viewing or browsing tools, and the saving-as-new-image behavior adds clarity.

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 this tool is for persistent, user-facing edits and contrasts it with ephemeral resource template transforms. However, it does not explicitly name alternative tools or say when not to use it, so it misses the full mark.

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