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

No annotations are supplied, so the description carries the full burden. It does add genuinely useful non-schema context: the response shape "Returns { image }" and the cost "1 credit", which matters for a metered generation endpoint. It says nothing about output resolution, whether the original is preserved, input size limits, or failure/refund behavior, leaving the mutation profile only partially disclosed.

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?

Three short sentences, front-loaded with the action and mode list, then return shape, then cost. Nothing is padded and there is no restatement of the name.

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 two-parameter image tool with no output schema, disclosing the return shape and credit cost covers the most important unknowns. What is missing is the comparative context against near-duplicate siblings and any constraint on input image size or output resolution, which the schema does not supply either.

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 description coverage is 100% and includes an enum with a documented default, so both parameters are already fully specified in structured data. The description's mention of clean-up/sharpen/denoise/lighting mirrors the enhanceType enum without adding format, default or interaction semantics.

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 and resource ("Enhance image quality") and enumerates the four concrete operations (clean-up, sharpen, denoise, lighting). It does not distinguish itself from overlapping siblings such as upscale_image, relight_image, photo_repair or dslr_transform, so an agent could hesitate between them.

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?

Usage is only implied by listing enhancement kinds; there is no explicit when-to-use, when-not-to-use, or named alternative. With siblings like relight_image and photo_repair in the catalog, the absence of routing guidance is a real gap.

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