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

Annotations cover safety hints (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false), and the description adds real behavior beyond them: operations are 'applied in order', the result is a brand-new image with its own page_url/image_url/download_url, and the original is preserved. It does not discuss failure modes, auth, or what happens with invalid operations, which keeps it short of a 5.

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?

Front-loaded with the core verb and resource, then the operation inventory, then the output/non-destructiveness fact. The long operation enumeration is dense but each item maps to a real capability; nothing is bloated or redundant.

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?

With no output schema, the description correctly explains the return artifacts (page_url, image_url, download_url) and the non-destructive write semantics, which is exactly what an agent needs here. Gaps remain for the quality, filename, and return_preview parameters, and for how format interacts with max_kb.

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 57%, and the description compensates by grouping operations by intent (rotate, flip, crop by pixels or aspect ratio, resize by width/height/percent/megapixels, plus the filter list) and by noting the optional format and max_kb behaviors. It is silent on the quality, filename, and return_preview parameters, so it adds meaning but not complete coverage.

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?

States a specific verb (edit) and resource (an uploaded image) and enumerates the concrete operation set the tool supports, so an agent knows exactly what transformations are available. It also implicitly separates itself from the siblings by stating the original stays unchanged and a NEW image is created, distinguishing it from delete_image and from a fresh upload_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?

The phrase 'Edit an uploaded image' plus the id schema description imply the prerequisite (an id from upload_image or edit_image), but the description never says when to prefer this over re-uploading or over get_image. No explicit alternatives or when-not conditions are given, so usage is inferred rather than stated.

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