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

With no annotations, the description carries the full burden and does well: it discloses the toll amount, the payment rails (Base or Solana via x402), and critically that a failed payment yields 402 instructions instead of data. It doesn't state rate limits or latency, but the cost/authorization profile is unusually well surfaced.

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 tight sentences, front-loaded with the tool's function followed by the cost model and fallback. The 'Mini's TrollBridge' branding is minor filler but costs almost nothing in length.

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?

No output schema exists, yet the description lists the returned data categories (type, balance, watchlist, risk flags) and explains the 402 failure mode, which is exactly what an agent needs before calling. Only the precise 402 payload structure and any rate limits are left unstated.

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 both parameters are already documented with descriptions and an enum for network. The description merely restates 'requires address and network' without adding format, validation, or example syntax, so the schema does all the work.

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+resource ('wallet address intel') and enumerates the returned fields (type, native balance, USDC watchlist, risk flags). None of the sibling tools (bounties, gas, prices, token_check, etc.) overlap this scope, so an agent can distinguish it immediately.

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?

Gives clear preconditions — both address and network are required, and payment of $0.05 USDC via x402 is mandatory — plus the fallback behavior when payment is unavailable. It does not explicitly compare against sibling intel tools, but no sibling covers this domain, so the guidance is practically complete.

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