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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds important context beyond that: it requires a bring-your-own-key API approach, costs $0.01/call via x402, and outputs one row per wallet. It also clarifies that no browser or RPC node is needed, which helps set expectations. However, it does not detail rate limits or potential error conditions, but the annotation coverage lowers the burden.

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 concise and well-structured: the first sentence states the core function and method, the second lists key outputs, and the third clarifies non-requirements and cost. Every sentence adds value, and the key information is front-loaded in the first sentence.

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?

Given the tool has 5 parameters, no output schema, and substantial annotations, the description is fairly complete for a tracker tool. It covers the data sources, output granularity, API key requirement, and pricing. It does not explain the exact response structure in detail, but the description's mention of 'balance, flagged transfers, and recent token activity' gives a reasonable preview. The lack of a formal output schema is mitigated by the clear output hints in the description.

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%, so the baseline is 3. The description does add some semantic value by linking 'flagged transfers above your ETH threshold' to minValueEth and mentioning 'one row per wallet' for the wallets parameter, but it largely restates concepts already in the schema. It does not provide deep additional parameter-level detail beyond that.

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 purpose: to track large native ETH and ERC-20 token movements for any wallet(s) via Etherscan's multichain API. It specifies the key actions (get current balance, flagged transfers, recent token activity) and distinguishes itself from siblings like wallet-airdrop-profile by focusing on movement tracking rather than profile analysis.

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 on when to use the tool: for large token movement tracking with no RPC node, wallet-connect, or browser needed. It implicitly differentiates from alternatives by highlighting its simplicity and API-based approach, though it does not explicitly name sibling alternatives or state when not to use the tool.

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