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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds that this is a pure probability calculation, but says nothing about cost — nonces accepts up to 250,000,000, and an agent has no warning that large runs may be expensive or how results are returned.

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?

One dense sentence that front-loads the primary probability and appends the nonces extension. No filler, though the clause structure is compressed enough that the two distinct outputs could be separated more cleanly.

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 return values need not be described, and the annotations cover safety. What remains missing is the mapping from game to required options and any note on the cost of large nonce runs — material for a tool with 4 top-level params and a 25-property nested object.

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 50%, and the description explains none of it beyond 'a setting' and 'a run of N nonces'. The nested options object is game-dependent (mines gems/bombCount, plinko rows/risk, dice target/isRollOver, etc.) and the description gives no rule for which options apply to which game — the single largest usability gap.

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 computation: the probability a Stake Original pays at or above a multiplier at a given setting, plus the chance at least one such payout falls inside a run of N nonces. The 'run of N nonces / Seed Hunter' framing distinguishes it from a plain payout-odds tool, though it never names the sibling stake_payout_odds it most resembles.

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?

There is no explicit when-to-use guidance, no exclusions, and no mention of the near-neighbour stakes_payout_odds or stake_crash_odds. The phrase 'the maths behind the Seed Hunter' gestures at a context but leaves the agent to infer the selection rule.

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