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

Annotations already declare non-read-only, non-destructive, non-idempotent, and the description adds the key behavioral fact that a new asset is produced and the source is untouched — exactly the reassurance needed given readOnlyHint=false. It also discloses operation ordering ('applied in order') and the max_kb meaning (1 KB = 1,000 bytes). It does not cover auth, rate limits, or failure behavior, so not 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?

The operation list is front-loaded and the two sentences carry no filler; the second sentence delivers the crucial new-image semantics. The long em-dash enumeration is dense but each term maps to a real enum value, so it earns most of its length.

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 usefully names the returned fields (page_url, image_url, download_url) so the agent knows what it gets back. Given 7 parameters and 57% coverage, a few inputs (quality, filename, return_preview) remain undocumented, but the core editing contract is complete.

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?

At 57% schema coverage the description adds real value: it clarifies the operations pipeline is order-sensitive and groups the enum values by category (rotate/flip/crop/resize vs. color and filter ops), plus explains max_kb as an output size ceiling tied to format. It leaves quality, filename, and return_preview unaddressed, and much of the op vocabulary is already in the enum/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?

States a specific verb (edit) and resource (an uploaded image) and enumerates the concrete transform set, so the agent knows exactly what capability this is. It also distinguishes itself from siblings by stating it creates a NEW image and leaves the original unchanged, contrasting with delete_image/get_image/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?

'Edit an uploaded image' plus the id parameter description establishes the prerequisite (an id from upload_image or edit_image), which is clear context for when to call this. It stops short of explicit exclusions or naming sibling alternatives for non-edit scenarios (e.g., use get_image to just inspect), so it is context-clear but not fully routing.

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