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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower, and the description still adds real operational context: the $0.05/call x402 price, the prepaid x-credit-token header requirement, the absence of a free tier, and no API key needed. It also discloses what it flags (unlimited allowance, no expiry, unrecognized spender), which is behavior beyond the annotations.

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?

Front-loads the core question ('Which apps/agents can pull funds from this Base wallet?') and then the mechanism, pricing, and input requirements. A few lines are promotional filler ('the primitive behind autonomous agent payments', 'agent-era drain check') but overall it is dense and readable.

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?

Output schema exists, so return values needn't be explained, and annotations cover the safety profile. The description still supplies everything an agent needs to call it correctly: the required wallet argument, cost model, auth header, and what the audit surfaces.

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 description coverage is 100% and there is a single required parameter, so the schema already carries the semantics. 'Required input: wallet' merely restates the required field without adding format or validity constraints, so the baseline 3 applies.

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 ('reconstructs a wallet's ACTIVE spend permissions from onchain approve/revoke events') and explicitly contrasts itself with ERC-20 approval tools, which maps onto siblings like token_approvals and approval_advisor. An agent can distinguish this from the surrounding approval/revoke tools without opening the schema.

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?

The framing as 'the drain check that ERC-20 approval tools can't see' implies when this tool is the right pick, but there is no explicit when-to-use/when-not guidance and no sibling named outright as an alternative (e.g. wallet_drain_watch, token_approvals). Usage must be inferred from positioning rather than stated.

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