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

Annotations already declare read-only/idempotent/non-destructive, yet the description adds what they cannot: the $0.001 per-call price, that the default return value is a paid x402 request rather than the data, that a P0 bearer key changes the behavior to an auto-paid call with price deduction, and that invalid input is rejected before any charge. That is exactly the extra context an agent needs to avoid a surprise charge.

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?

Single paragraph, front-loaded with the 'Use when' trigger followed by output behavior, pricing, and auth. It is dense and slightly run-on, but nearly every clause (price, payment path, schema link, pre-charge validation) carries distinct operational value.

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 tool with a dual payment/execution mode and no output schema, the description covers the return shape in both modes, cost, auth header format, key purchase URL, and error-before-charge behavior. An agent has everything needed to decide whether to call it and how to interpret the response.

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 description coverage is 100%, so all seven parameters are already documented in structured fields. The description restates the same parameters (n in [min,max], choices, unique, round) and adds only the 'choices=a,b,c' comma format hint, which is marginal beyond the schema. Baseline 3 applies.

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?

The description names a specific verb and resource ('publicly verifiable random numbers: n integers in [min,max] ... a pick from choices=a,b,c or a unique draw') and names the underlying mechanism (drand / League of Entropy beacon round). No sibling tool produces randomness, so the agent can route here unambiguously.

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?

'Use when you need publicly verifiable random numbers' sets the trigger condition clearly, and the two execution paths (no key = returns the paid x402 request URL; P0 key = tool makes the paid call itself) are spelled out. It does not name any alternative among siblings, but none exists in the list, so the gap is minor.

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