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

With no annotations, the description carries the full burden. It discloses the 50-address cap, Base-only ETH/USDC scope, dual GET/POST input formats, and 50% pricing, but does not cover authentication/payment requirements, rate limits, or failure behavior for invalid addresses.

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 purpose, capacity, price, and input formats are front-loaded in the first two sentences. The second sentence about 'pipeline agents, x402 payer-vetting observatories and copy-trade desks' is somewhat marketing-heavy, but the use-case list that follows earns its space.

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 and no annotations, but the description states the returned assets, network, input formats, cap, and pricing. It is sufficient to invoke the tool correctly, though it leaves gaps around payment/auth and response/error shape.

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 is empty, so the baseline is 4. The description adds important meaning by documenting the `addresses` input, the maximum of 50 EVM addresses, and both `?addresses=0xA,0xB,…` and POST `{"addresses":[…]}` syntax. This compensates for the schema being effectively silent, though the schema's `additionalProperties: false` creates ambiguity.

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 verb and resource: bulk wallet vetting returning Base ETH and USDC balances for up to 50 EVM addresses. It clearly distinguishes batch from per-address calls via the 'ONE call' and '50% of the single-call price' framing, though it does not name a specific sibling tool as the single-address alternative.

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?

Explicitly lists use cases: batch wallet health checks, airdrop/allowlist screening, payer vetting at scale, and treasury monitoring. The batch-vs-single distinction is implied through price and throughput, but there is no explicit 'do not use for a single address' exclusion.

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