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

Annotations declare the safety profile (not read-only, idempotent, not destructive); the description adds the payment lifecycle that annotations cannot convey — the initial unpaid call, the PaymentRequired response, the required payment meta field, and the fact that the invoice is only marked paid once the facilitator settles. It stops short of describing failure/retry behavior for a rejected or expired payment.

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 tight sentences, front-loaded with purpose before the mechanics of the payment handshake. No filler; every clause carries operational meaning.

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 one-parameter tool with no output schema, the description covers the full invocation cycle and the settlement outcome. Remaining gaps (amount/currency selection beyond 'exact USDC on Base', error handling) are minor and partly implied by the protocol reference.

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 100% for the single invoice parameter, so baseline is 3, but the description adds semantics the schema omits: the settlement meta field (_meta["x402/payment"]) the agent must supply on the second call. That extra invocation parameter is real added value.

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 ('Pay a Billify invoice') plus the protocol used, which cleanly separates it from get_invoice (read) and verify_seller. An agent can identify the tool's role without inspecting the schema.

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?

Gives an explicit two-step invocation procedure: call once to obtain PaymentRequired, sign it, then call again with _meta["x402/payment"]. That is strong operational guidance, though it never contrasts this tool with its siblings or says when not to use it.

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