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

The annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is covered. The description adds one trait not present in annotations: the call consumes credits and the pricing/balance siblings to consult first. It says nothing about what is destroyed, whether the original image is overwritten, or whether the operation is asynchronous.

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 cost disclosure is front-loaded and the purpose follows immediately, with no filler sentences. The trailing "Params:" enumeration is redundant with the schema and could be dropped, costing it a point.

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 four-parameter, credit-spending mutation with no output schema and no parameter documentation, the description leaves key questions open: whether the response is an image or a job id needing kreavo_check_image_status, what models and aspect ratios are accepted, and what happens to the source image. The presence of a status-check sibling strongly suggests an async flow that is never mentioned.

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 0%, so the description must carry parameter meaning, but it only restates the four property names with a question mark for the optional ones — information the schema already encodes via the required array. No valid model values, aspect_ratio formats, or prompt constraints are explained.

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?

"Edit/inpaint an existing image" gives a specific verb pair and object, and the phrase "existing image" implicitly separates it from kreavo_generate_image and kreavo_virtual_tryon. It never names the sibling it competes with, so the differentiation is inferred rather than explicit.

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 routes the agent to kreavo_list_models for pricing and kreavo_get_credits for balance, which is genuine when-to-use context for the cost check. However, it gives no guidance on when to edit versus generate a fresh image, and no prerequisites such as image ownership or upload requirements.

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