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

Annotations already establish readOnly, non-destructive, non-idempotent, closed-world behavior, so the bar is lower. The description still adds genuine value beyond them: it discloses the trust model (server seed revealed with the result) and an important caveat (no prior commitment and no host-bias proof), which tells the agent this randomness cannot be pre-verified.

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, front-loaded with the mechanism and followed by the fairness caveat. Nothing is padded, though the extreme brevity leaves useful detail (what the draw returns, how bet/client_seed interact) unaddressed rather than deliberately trimmed.

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?

There is no output schema, so the description carries some burden for explaining the return value; it mentions that the server seed comes back with the result but does not describe the drawn outcome or shape. For a zero-required-parameter read-only tool this is adequate but incomplete.

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 the enum meanings ('cho' = even, 'han' = odd) and the optionality of client_seed are already fully documented in the schema. The description adds no parameter syntax or semantics beyond that, making the baseline 3 appropriate.

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 concrete mechanism ('SHA-256 dice draw') and implies a cho/han random outcome, but it never states plainly that it produces a random cho/han result for the caller. It also fails to distinguish itself from the sibling economy_chohan_arbitrate, so an agent cannot confidently route between the two from the description alone.

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?

No when-to-use, when-not-to-use, or alternative guidance is given. With a nearby sibling (economy_chohan_arbitrate) that plausibly overlaps, the absence of any routing information is a real gap.

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