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

Annotations already establish a safe read-only idempotent operation, and the description goes well beyond them: it discloses the x402 price per call ($0.003 USDC), that errors are free, that invalid input returns 400 without charge, which data sources back which fields (public Base RPC vs free Blockscout), and the null-with-note policy that guarantees no invented values. firstSeen being deliberately null is called out so the agent doesn't misread it as an error.

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 pricing/error contract is bracketed and front-loaded, and the returned-field list follows immediately, so the important information is first. It is dense and parenthetical-heavy, and the null-handling policy is stated twice (general rule plus the firstSeen special case), which costs a little length without much added clarity.

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?

There is no output schema, so the description carries the return-value burden itself and does it by enumerating every returned field plus null semantics. Pricing, error behavior, data provenance, and the not-investment-advice disclaimer are all covered, leaving no obvious gap for an agent to call this correctly.

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% with a single optional address parameter already documented including its default (vitalik.eth), so the schema carries the semantics. The description's only added signal is the 400-on-invalid-input contract, which is behavioral rather than parameter guidance. Baseline 3 is appropriate.

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 concrete verb and resource ('one-call wallet profile') and enumerates exactly what it returns: account type, nonce, balances with USD, tx counts, 7/30-day activity, last seen, token count. That enumeration makes its scope legible against single-purpose siblings such as base_wallet_balances. It never names a sibling explicitly, so the differentiation is inferable rather than stated.

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' implies this is the bundled alternative to calling several single-purpose tools, which is implied usage guidance. However, it never states when to prefer this over base_wallet_balances or base_risk, nor when not to use it (e.g. for contract-level or token-level questions). The agent must infer routing from the returned-field list.

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