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

No annotations, so the description carries the full burden. It discloses a lot of behavioral detail — a ~50-minute observation window, the classification label set, and the GET-query vs POST-body dual invocation. It is silent on auth requirements, rate limits/cost, and what happens with an unknown or malformed address, which matter for a paid intelligence endpoint.

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?

Dense but front-loaded: purpose first, then the invocation form, then the returned fields, then the classification set. It is a long single block and could be split into discrete sentences, but nearly every clause carries information an agent needs.

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 and no annotations, the description does the heavy lifting by enumerating the return fields and the exact classifier labels, which is exactly what an agent needs to decide relevance. Remaining gaps — error behavior, auth, and the GET/POST vs zero-parameter schema conflict — are modest but real.

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 declares zero properties with additionalProperties:false, so the description is the only source of the required address argument and its two transport forms (?address=0x… on GET, {"address":"0x…"} on POST) — information the schema cannot supply. This is above the 0-param baseline, though it sits in tension with the schema's closed-object declaration rather than resolving it.

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 resource (deep wallet profile) and enumerates exactly what is returned: ETH+USDC balances on Base, tx count, contract detection, ~50 minutes of USDC payment flows, counterparty concentration, and a classification taxonomy. An agent knows precisely what it gets. It does not, however, distinguish itself from sibling akari_wallet_intel, which is presumably the closest alternative.

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?

Usage is implied by 'x402 payer intelligence' — profile a wallet to judge whether it is an autonomous-agent payer. But with 20 siblings including akari_wallet_intel, the description offers no when-to-use/when-not or alternative routing, leaving the agent to infer which wallet tool to pick.

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