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

Annotations already cover read-only/idempotent/non-destructive. The description adds valuable operational context: pricing ($0.06/call on x402/Base), the optional prepaid x-credit-token header, the free daily call, and the fact that no wallet/API key is needed. These go beyond annotations and affect how an agent invokes the tool.

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 sentences are dense but each adds relevant info: the verdict behavior, the single-input requirement, and the pricing/auth header. It's front-loaded with the main purpose before billing details. Minor overstuffing in the payment sentence prevents a perfect score.

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 tool with an output schema and read-only annotations, the description covers the purpose, the expected output concept (synthesized verdict with observations), input requirements, and operational constraints (cost, auth header, no API key). Nothing essential 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?

The schema already documents address at 100% coverage. The description only restates 'Required input: address' and gives no extra detail about address format, chain scope, or validation. It adds no meaning beyond the schema, so a 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 capability ('Claude-written verdict on any wallet') and defines the pipeline: aggregates net worth, age/activity, recent transactions, then synthesizes a verdict with key observations. This clearly separates it from sibling wallet tools that return raw metrics (wallet_networth, wallet_activity, wallet_summary).

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 positions itself as 'the flagship wallet report' and 'one call, agent-ready wallet intelligence,' signaling that this is the high-level synthesized answer rather than a raw data pull. It does not explicitly name sibling alternatives or say when to avoid it, so it falls short of full routing guidance.

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