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

With no annotations provided, the description fully discloses important behavior: cost via x402, USDC on Base, the 200-token/100-transaction limits, native-coin exclusion, and the partial-response flags such as provider_limited and token_balances_complete. This goes well beyond a generic description.

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 description is dense but efficient: every sentence carries essential information about pricing, limits, exclusions, and partial-response behavior. There is no filler or unnecessary repetition of the schema.

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?

For a single-parameter tool with no output schema and no annotations, the description is notably complete. It covers the input, cost, limits, native-coin exclusion, and response metadata fields, leaving an agent well-equipped to select and invoke the tool 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?

The input schema already documents the single address parameter at 100% coverage, including the format '0x...'. The description only restates that the snapshot is for one address and does not add meaningful parameter-level semantics 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?

The description clearly identifies the tool's operation: it returns a Base wallet snapshot with quantified limits (200 ERC-20 balances, 100 transactions) for one address. It also states exclusions, such as native coin balances, and the paid provider nature, which helps distinguish it from the sibling wallet_watch_snapshot.

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 description provides clear context: paid x402 access, explicit caps, and partial-response behavior, so an agent knows when this tool is appropriate for a comprehensive wallet snapshot. However, it does not explicitly name wallet_watch_snapshot as an alternative or give when-to-use versus when-not-to-use guidance.

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