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

With no annotations, the description carries the full burden and does most of it: it discloses output contents (each result plus head/tail tally), randomness quality (cryptographic, not Math.random), auth requirements (no API key, no account) and cost ($0.005/call via x402 USDC). Minor gaps remain on rate limits, failure modes, or response shape, but pricing and auth disclosure is unusually strong.

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?

Front-loaded with the triggering condition and free of filler, but the first sentence is a long run-on that chains use case, output shape, and randomness quality together. Nothing is wasted, though it could be broken for scannability.

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 one-parameter, no-annotation, no-output-schema tool, the description covers what it returns ('each result and the tally'), how it authenticates, what it costs, and when not to use it. An agent has everything needed to call it and to pay for it correctly.

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%, with the count range (1-100) and default of 1 already documented in the schema. The description mentions 'one or more fair coins' but adds no format, cost-per-coin, or edge-case semantics beyond that, so the 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?

States a concrete verb+resource: 'one or more fair coins, each result and the tally of heads and tails,' with the cryptographic-randomness qualifier. It explicitly names the siblings it is not (random_pick at /v1/random/pick, random_shuffle at /v1/random/shuffle), so the agent can route 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?

Opens with an explicit use case ('break a tie or split a test and cannot be seen to have chosen') and immediately follows with negative routing to the two alternatives for >2 options and list ordering. The decision boundary is fully specified.

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