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

With no annotations, the description carries the full burden; it discloses that data is live via raw RPC and scoped to Base, which is useful behavioral context. However, it says nothing about rate limits, failure modes for invalid/non-EVM addresses, or what the response contains, leaving meaningful gaps for a read tool with zero annotation coverage.

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?

Two tight sentences with the core capability front-loaded, then usage and the escalation path. The inline URL path detail is slightly noisy but costs little and aids disambiguation.

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 and no annotations, so the description must convey return shape on its own; it names ETH and USDC balances but not the other fields an agent would receive. It also leaves the address-passing mechanism ambiguous against an empty schema, making it only adequate for a tool whose only input is undocumented structurally.

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, yet the description instructs to 'pass ?address=0x…', so it does supply the one input the schema omits. That is valuable, but it also creates tension with the structured schema (the address has no declared slot), so it does not cleanly earn the zero-parameter baseline of 4.

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 — on-chain wallet intelligence for any EVM address on Base, returning live ETH and USDC balances via raw RPC. It also differentiates scope from a richer variant (the deep path adding payment flows, counterparties, agent classification), so an agent can tell the two apart.

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?

Enumerates concrete use cases: wallet health checks, balance lookups, funding verification, and x402 payer vetting. It names the alternative (the deep variant) and what extra it provides, though it gives no explicit 'when not to use' or prerequisites (e.g., rate limits, chain restrictions beyond Base).

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