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

Annotations cover the safety profile (readOnlyHint=true, openWorldHint=true), so the bar is lower, and the description still adds material behavior: responses are signed, the observation window is 30 days, and the call is paid at $0.01 USDC via x402 on Base or Solana. The payment/authentication requirement is exactly the kind of thing annotations cannot convey. It does not describe pagination, rate limits, or failure modes for unfunded wallets.

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 returned data are front-loaded in the first sentence, and 'Signed.' plus the price clause are terse and informative. The first sentence is a long enumeration, but each item (services, grades, USDC volume, payers, fake-volume signals) earns its place by describing the output.

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 describe return values, and it does so concretely, listing the report sections and the anomaly signals it surfaces. The remaining gaps are the address format, the payment mechanics in more detail, and error behavior, which are secondary for a read-only single-parameter check.

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% for the single 'address' parameter, so the description has to carry the meaning. The phrase 'x402 seller wallet on Base' implies the address is the seller's wallet, which is useful, but it never specifies the expected address format or chain, and the mention of Solana as a payment rail introduces ambiguity about which chain the address belongs to.

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 ('Checks for an x402 seller wallet on Base') and then enumerates exactly what the report contains: payout services with grades, 30-day USDC receipts, payers, repeat payers and fake-volume signals. That is far more informative than the title. It stops short of explicitly distinguishing itself from close siblings such as checks_service or checks_top, so it is clear but not sibling-differentiated.

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?

There is no when-to-use or when-not-to-use guidance and no alternative tool is named, even though checks_service, checks_top and checks_changes sit right beside it in the same family. The agent must infer that this is the seller-side counterpart from the name alone. Only implicit usage context is present.

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