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

With no annotations provided, the description carries the full burden. It clearly signals a read-only operation via 'Retrieve static game rules' and 'static', and discloses cost explicitly with 'Free -- no payment required'. It also enumerates all returned data, offering good transparency without asserting any side effects.

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 compact and front-loaded with the primary purpose. Subsequent sentences expand on returns and usage. The duplicate mention of 'free' (once in prose and once as pricing metadata) is minor and does not detract from overall clarity.

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 must explain return values, and it does so thoroughly: flip cost, randomness source (Chainlink VRF), pot payout rules (2-hour and jackpot), denomination model (ETH pots, USDC payments), and strategies (match vs beat). This fully covers the informational scope for a zero-parameter, read-only tool.

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?

The tool has zero parameters and the input schema is empty, so there is nothing to explain. The description appropriately focuses on the output rather than parameters. The baseline for 0 params is 4, which is fitting here.

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 uses a specific verb 'Retrieve' and precisely names the resource: static game rules, denomination model, pot mechanics, and strategy explanations. It explicitly lists the contents (flip cost, Chainlink VRF, pot payout rules, etc.), which clearly distinguishes it from sibling tools like flipr_flip or flipr_pot.

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?

The description explicitly instructs 'Call this first to understand the game before using other tools,' which provides clear when-to-use guidance. It does not explicitly mention when not to use or name alternatives, though the sibling list makes the context evident.

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