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

Annotations only declare the mutation/open-world profile; the description adds the economically critical facts the annotations cannot: the 0.05 USDC price on Base (eip155:8453), the x402 settlement handshake and where the response lands, and the no-charge guarantee for failed calls. That is substantial behavioral context beyond the hints, with no contradiction of readOnlyHint=false or destructiveHint=false.

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 purpose and cost are front-loaded in the first sentence, and the payment mechanics follow in a compact block. The metadata key paths (params._meta["x402/payment"], result._meta["x402/payment-response"]) are verbose but load-bearing for correct invocation. Minor redundancy: "One call, one picture" repeats the first clause.

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 must carry the return contract, yet it only explains where the payment settlement appears in result._meta — it never says where the actual image payload lands (URL, base64, MIME type) or how it is delivered. For a paid image generator that is the single thing an agent most needs after the payment flow.

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%, so the schema already documents all five parameters including the optional seed, shape, style and negative fields. The description only restates the 400-character prompt bound already present in the schema and says nothing extra about how seed, shape, or negative affect the output. Baseline 3 applies.

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?

"Verse paints one picture from a text prompt (up to 400 characters), safe for work. One call, one picture." gives a specific verb (paints), a specific resource (one image), a hard input bound, and a content policy. It is immediately separable from siblings like paid_answer, paid_translate, or paid_digest, which are all text-oriented.

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?

It spells out the exact invocation protocol: call once without payment to receive PaymentRequired terms in structuredContent, then re-call with the signed PaymentPayload in params._meta["x402/payment"]. It also states the failure case is never charged, which tells the agent retrying is safe. It does not say when to prefer an image tool over a textual sibling, so it falls short of explicit alternatives/exclusions.

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