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

Annotations already cover read-only, idempotent, and non-destructive behaviorcase. The description adds meaningful context beyond annotations: pricing per call, x402/Base payment rail, prepaid header for unlimited calls, free daily quota, and the lack of wallet/API key requirements. This helps an agent understand access costs and prerequisites. No contradiction with annotations.

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 description is front-loaded with the core purpose and remains information-dense, covering inputs, output, pricing, and prerequisites. It has minor redundancy — 'AI-written verdict' and 'AI synthesizes a verdict' — and the pricing block is secondary, but it earns its place by informing cost-sensitive agents.

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 single-parameter read-only tool with an output schema and comprehensive annotations, the description covers everything needed to call it correctly: the input, the purpose, the synthesized output nature, access prerequisites, and pricing. No critical information is missing.

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% for the single address parameterretty. The description simply restates 'Required input: address' and adds no format, network, or example details beyond what the schema already provides. Baseline 3 is appropriate.

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 names a specific deliverable — an AI-synthesized wallet verdict — and enumerates concrete inputs: net worth, age/activity, recent transactions. It differentiates itself from the many sibling wallet tools by being the 'flagship wallet report' that aggregates multiple dimensions into one agent-ready call rather than a single metric.

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 clear context: use this when you need an all-in-one AI verdict on a wallet, and it states prerequisites are minimal ('Required input: address', 'No wallet or API key required'). It does not explicitly name alternatives or state when not to use it, but the flagship/aggregate positioning makes the primary use case clear.

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