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: it discloses the payment rail (x402 on Solana or Base), the exact cost (0.025 USDC), the batch ceiling, and that output equals the full check per mint. It omits failure/partial-batch behavior and latency, which keeps it short of a 5.

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?

One front-loaded sentence that opens with the usage condition and follows with the cost/limit facts. Every clause carries information; nothing is padding.

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?

For a single-parameter tool with no annotations and no output schema, the description covers when to use it, what it costs, and how the output relates to the sibling check. The remaining gap is that it never actually describes the returned screening fields, deferring entirely to "the full check."

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 0% for the single `addresses` parameter, so the schema documents nothing beyond type and maxItems=10. The description implies the values are mint addresses and reiterates the 1–10 batch range but adds no format or ordering guidance, leaving the parameter only partially illuminated.

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: batch-screening up to 10 Solana tokens, with the scope limit called out. It also anchors itself to the sibling concept ("same output as the full check for each mint"), so an agent can tell it apart from the single-token check without opening either schema.

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?

Gives a clear trigger ("Use when screening up to 10 new Solana tokens at once") with concrete scenarios (sniping, watchlists). It does not explicitly name solana_token_check as the alternative for a single mint or state when-not to batch, so routing is implied rather than spelled out.

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