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

With annotations present, this goes well beyond them: it enumerates the server-side checks (Base chain, native USDC contract, recipient, sender, exact amount, invoice window, finalization), states the operation never moves funds, notes a transfer cannot be credited twice, and confirms no authentication is required. That is substantially more than readOnly/openWorld/destructive/idempotent hints provide.

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?

It is dense but front-loaded with the workflow and constraints, and every clause (checks performed, retry loop, no-move guarantee, disambiguation from MPP/x402, public access) carries distinct information. It runs slightly long and could trim the alternative-endpoint caveat, but nothing is padding.

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 3-required-param mutation with an output schema available, the description covers prerequisites, caller authorization, verification criteria, idempotency protection, retry behavior, and auth posture. Return values are correctly left to the output schema, so an agent has everything needed to invoke it correctly.

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 has to carry the parameter burden, and it does for transaction_hash and signature (what they are and how the signature must be produced). funding_id is only implied via the invoice reference and is never directly explained, leaving one of three required parameters under-specified.

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?

The description states a specific action (verify/claim a signed USDC transfer) against a specific resource (base_usdc invoice funding), and explicitly separates the operation from retrieval siblings like get_funding by defining it as a verification/claim step. It also rules out two named alternatives (MPP, x402), so an agent knows exactly what class of operation this is without opening a 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?

It gives an explicit precondition (after paying a base_usdc invoice), the exact prerequisite action (sign the signature_message with EIP-191 personal_sign), the two artifacts to submit, the caller restriction (only the declared sending wallet), and retry guidance (repeat until paid). This is close to a complete when/when-not/alternative specification.

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