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

Annotations already declare readOnlyHint, idempotentHint, and closed-world behavior, so the safety profile is covered. The description adds meaningful behavioral context by naming the exact statistics returned, including average rounds between hits and the instant 1.00x chance, which go beyond the annotations.

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?

The description is a single dense sentence that front-loads the core purpose and enumerates the outputs without filler. It is efficient, though the long list of metrics makes it slightly harder to scan than a short bulleted structure would.

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?

An output schema exists, so the description need not explain return values in full. It still names the returned metrics, covers the required target and optional rounds semantics, and works alongside annotations that confirm safe read-only calculation. Minor gaps remain around sibling differentiation but nothing essential for correct invocation is missing.

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 67%, and the description compensates well by clarifying that target is a cash-out multiplier and that rounds relates to the chance of at least one hit within N rounds. It also indicates the two game types, Crash and Slide. The enum parameter 'game' still lacks a description in the schema, but the description covers it adequately.

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 clearly states the computed outcomes: hit probability for a cash-out target, return, average rounds between hits, hit chance within N rounds, and instant 1.00x chance. It is specific enough to distinguish this from general payout tools, but it does not explicitly differentiate itself from close siblings like stake_crash_droughts or stake_payout_odds.

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?

Usage is implied by the listed calculations: use this when you need Crash/Slide target odds, return, or hit timing. However, there is no explicit statement of when to use this versus sibling tools such as stake_crash_droughts or stake_payout_odds, nor any exclusions or prerequisites.

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