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

Annotations only declare readOnlyHint and openWorldHint; the description adds genuinely useful behavioral context beyond them: the tool is paid (0.05 USDC via x402 on Solana or Base) and the batch is half the per-token price. It does not cover failure behavior for invalid mints or partial batches, so it stops 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?

Two short sentences, zero filler, with the payment cost front-loaded before the functional description. Slightly clipped to the point that the return value is left unstated.

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 paid, single-parameter tool with no output schema, the description covers price, chain, and batch size but says nothing about what a 'full risk score' contains, how payment is settled/authorized, or what happens if fewer than 10 mints are supplied. Adequate but leaves real gaps for an agent invoking a paid call.

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?

One parameter with 0% description coverage per the metric, though the schema itself carries the base58 mint constraint and min/max items. The description reinforces the batch size cap ('up to 10') but adds no format, ordering, or deduplication semantics beyond the schema.

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 ('Full risk score for up to 10 Solana mints in one call'), so the agent knows this is a batch scoring tool. It implies differentiation from solana_token_quick_check via 'Full' and from solana_token_safety via the batch/10-mint scope, but never names either sibling explicitly.

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 'up to 10 ... half the per-token price' phrasing implies this is the choice when you have multiple mints and want cost savings, but there is no explicit when-to-use statement, no condition for preferring solana_token_quick_check or solana_token_safety, and no mention of the per-token alternatives' tradeoffs.

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