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

Goes well beyond the readOnly/openWorld annotations: discloses the ~5,000-block (~3h) lookback window, the exact labeling sources, the deterministic/no-LLM nature, and critically a $0.012 USDC x402 payment that must be supplied in _meta['x402/payment']. That payment requirement is exactly the kind of behavioral detail annotations cannot convey.

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?

The leading capability enumeration is front-loaded and useful, but the inline example output is long, eats a large share of the text, and is visibly truncated mid-string ('"walletType":"' then cuts to pricing), which reads as an editing error rather than an intentional summary.

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 correctly takes on the job of describing return values, and it does so with concrete field names and a sample. The truncated example and the absent sibling comparison keep it from being fully complete.

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?

Only one parameter and the schema already documents it at 100% coverage ('EVM address on Base'). The description repeats the Base/EVM context but adds no format, checksum, or validation detail beyond the schema.

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 and enumerates exactly what the profile returns (holdings with USD, nonce, EOA/contract, ERC20 flow over ~5,000 blocks, labeled counterparties, walletType). However it never distinguishes itself from closely named siblings like base_wallet or wallet_portfolio, so an agent must guess which 'wallet' tool to pick.

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?

'One-call Base wallet profile' implies this is the consolidated alternative to narrower tools, and 'Free public data, deterministic, no LLM' hints at when it beats ai_* siblings. But there is no explicit when-to-use vs. base_wallet/base_erc20_balance/wallet_portfolio guidance.

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