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

Annotations only cover readOnlyHint and openWorldHint; the description goes well beyond by disclosing the randomness provenance (drand quicknet beacon, server secret, optional HF noise), rate limiting, and verifiability of the round. It does not state failure modes when the beacon or receiver is unavailable, which is the one meaningful gap.

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 core action, then provenance, then constraints in one dense but coherent sentence. The enumeration of response fields (round, signature, nonce, commitment, URL, physical block) is partly redundant given an output schema exists, which is the only bloat.

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?

With an output schema present, return-value detail is not required, and the description still supplies the provenance, verification path, and rate-limit context an agent needs. Only the absence of sibling differentiation keeps it short of complete.

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%, and the schema already documents both min and max as inclusive integer bounds with defaults, so the description's '[min, max]' phrasing adds nothing new. Baseline 3 applies when the schema does the heavy lifting.

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 with precise scope: 'Return a uniformly distributed random integer in [min, max]'. It also explains the entropy source, which distinguishes it substantively from a plain RNG. However, it never names or contrasts with its sibling random_int_signed, so the agent must infer which to pick.

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?

'Free and rate-limited' gives an implied usage constraint (cost and throttling), which is more than nothing. But there is no explicit when-to-use, when-not-to-use, or routing to random_int_signed/status, so the agent is left to guess between the two integer tools.

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