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

With no annotations, the description carries the full burden of behavioral disclosure. It usefully adds the cost ($0.005 USDC), the EVM chain scope, and the specific data fields returned, which helps set expectations. However, it does not state whether the operation is read-only, whether payment is required before execution, or any side effects, though 'snapshot' strongly implies a non-mutating read.

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?

A single concise sentence packs the core purpose, key outputs, and cost with no filler. It is front-loaded and every phrase earns its place, making it easy to scan.

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?

While an output schema exists, the description lacks essential operational context: no usage guidance, no parameter value constraints, no mention of how payment interacts with the cost, and no explanation of the 'fresh-wallet flag' semantics. An agent would likely need to probe the schema or make guesses about chain and payment values.

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 0% and the description barely helps disambiguate the parameters. It mentions EVM chains and address implicitly, but does not explain valid chain values, address format, or the role of the optional 'payment' parameter despite mentioning a cost. The agent cannot determine how to populate 'payment' or what chain strings are accepted.

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 resource (on-chain wallet) and the key outputs (contract/EOA type, tx count, native balance, fresh-wallet flag), which distinguishes it from sibling tools like token_snapshot and contract_check. However, it lacks an explicit verb like 'retrieve' or 'fetch', relying on 'snapshot' to convey the action.

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?

No guidance is given about when to use this tool versus alternatives such as token_snapshot or contract_check. The description implies a wallet-focused use case but provides no when-to-use, prerequisites, or exclusion criteria, leaving the agent to infer the appropriate context from sibling names.

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