edit_image

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

The description reveals that the tool always edits the original image and saves as a new one, and explains the persistence difference from LLM-facing transforms. This adds value beyond the annotations, which only indicate readOnlyHint=true (potentially contradictory).

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 that front-load the core purpose and immediately provide context. Every sentence adds value without 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?

Given the tool's simplicity (one parameter, no output schema), the description fully covers the interactive editing workflow and clarifies the distinction from transient LLM transforms. No critical gaps remain.

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 already fully documents the single parameter (image_id) with a description. The tool description does not add further semantic detail about the parameter, so a baseline score of 3 is appropriate.

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 opens an image for interactive editing with specific operations (crop, rotate, flip) and explains the workflow (user edits in UI, saves as new image). It distinguishes from resource template transforms, making the purpose unambiguous.

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 contrasts this tool with ephemeral resource template transforms, guiding the agent to use this for persistent, user-facing edits. It does not explicitly mention siblings like show_image, but the context is clear enough for most cases.

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