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

With no annotations, the description carries the full burden and does well on the essentials: it discloses the batch cap of 10, the deterministic ordering (ranked by realized PnL), the exact payload fields, and that the call is paid at $0.015 USDC. It stops short of failure semantics — whether the charge still applies if an address is invalid or the call errors, and what happens above 10 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?

Two sentences, zero waste, and front-loaded with the return payload and batch limit before the calling convention and price. Every clause carries information an agent needs (fields, cap, ordering, input format, cost).

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?

With no output schema and no annotations, the description must describe returns and does — it lists the four returned metrics and the sort order. The price and address cap complete the picture for a one-parameter batch call. The remaining gap is error/partial-failure behavior, which matters for a paid batch tool but is a minor omission here.

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?

There is a single parameter at 100% schema description coverage, so the schema already documents format and the 10-address limit. The description restates the comma-separated convention and adds "Solana" as the chain constraint, but contributes no syntax detail beyond the schema, making 3 the correct baseline.

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 ("Quick screen ... for up to 10 Solana wallets") and enumerates exactly which metrics come back (realized PnL, win rate, bot flag, smart-money flag) plus the ranking order. An agent can tell this is the batch variant of a screening call without opening the schema. It never names wallet_quick or wallet_profile as the single-wallet alternatives, so the sibling boundary is only inferred from the word "batch".

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?

Usage is implied rather than stated: "in one paid call" and "up to 10" signal that this is the bulk/cheap path versus per-wallet tools, and "Pass addresses comma-separated" gives the calling convention. There is no explicit when-to-use/when-not guidance, no exclusion for when fewer than two wallets should go to wallet_quick, and no guidance on partial or invalid addresses.

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