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

Annotations only declare readOnlyHint and openWorldHint; the description goes well beyond them by explaining score mechanics (bundled buyer wallets counted once, wash-pattern removals, 'not scored yet' with progress, never a 0). It stops short of disclosing failure behavior for an unknown identifier or any latency/rate characteristics of the chain lookup.

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 a single front-loaded sentence with no filler, leading with verb and resource before the payload details. The cost is density: three stacked parentheticals make it hard to skim, though each clause does carry real information.

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 carry the return-value burden, and it names every returned field class (owner/agent wallet, Fivebar Score with buyer and seller semantics, x402 screen states, flags, clusters). An agent needs nothing else to decide whether the response answers its question.

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 coverage is 100% and the single parameter already carries an example, so the schema does the heavy lifting. The description adds value by enumerating that the query may be an ERC-8004 ID, a wallet address, or a name, which clarifies the union-type acceptance more broadly than the schema's one example.

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 (look up) and resource (AI agent on Robinhood Chain) plus the three accepted identifiers (ERC-8004 ID, wallet address, name). The returned artifact set (owner, agent wallet, Fivebar Score, x402 record, flags, clusters) makes it unmistakable next to siblings like wallet_holdings or x402_stats.

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?

"Use before paying or trusting an agent" gives a clear triggering situation rather than leaving usage implicit. It does not, however, say when NOT to use it or how it relates to the overlapping sibling check_seller, so an agent must still infer the split between the two.

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