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

With no annotations, the description carries the full load and does a lot: it declares the operation is PAYWALLED, gives the exact price ($0.025) and accepted currencies (USDC on Arc, USDC on Solana, XNT), names the paid endpoint, and specifies the 25-item cap and sort order. What it does not disclose is the actual result payload once paid, or failure behavior on invalid/mixed ids.

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?

Four dense fragments, front-loaded with the paywall flag and capped scope, with zero filler. Every clause carries a distinct fact: cap, sort order, payment output, price/currencies, and the sibling alternative.

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 the description compensates by stating that the call returns x402 payment instructions and the endpoint path, plus the ordering of the eventual result. For a one-parameter tool this is close to complete, though it leaves the post-payment response shape and invalid-input behavior unstated.

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 coverage is 100% and the single 'ids' parameter is fully documented, so the baseline is 3. The description's 'up to 25 Arc tokens or pool ids' mirrors the schema description rather than adding format or validation details (e.g. whether addresses and pool ids can be mixed in one array).

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 operation (bulk exit check) with an explicit scope cap (up to 25 Arc tokens or pool ids) and an ordering rule (worst first by cannot sell / heavy loss / cannot buy), which conveys what an 'exit check' actually evaluates. It also names the sibling it is not (arc_exit_check), so the agent can separate the two without opening schemas.

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?

Clearly routes single-token work to arc_exit_check ('For one token use arc_exit_check'), which is an explicit alternative with a selecting condition. It also flags the paywall and the x402 payment path, so the agent knows a payment step is required before results. It does not state when the bulk call is preferable beyond the count (e.g. batch economics), so it stops short of full when/when-not coverage.

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