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

Annotations already declare readOnlyHint/non-destructive, so safety is covered; the description adds real behavioral context by stating the computation is exact over unseen cards rather than the Rule of 2 and 4 approximation (citing ~6 points error on a 15-out draw). It also discloses what output changes when outs is omitted, though it does not describe output shape in detail.

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 decision and returns, then justified with the formula and accuracy caveats. Four sentences with parenthetical examples are dense but each supports the 'use this instead of arithmetic' claim; slightly long but no filler.

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, and the description compensates by enumerating the return values (pot odds, break-even equity, exact hit chance, call/fold verdict). The conditional behavior of outs/street is spelled out, so nothing needed to call it correctly 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 100%, so parameters are already documented and a 3 is the baseline. The description goes beyond the schema by tying pot and bet together via the break-even formula (call/(pot+bet+call), pot-sized=33.3%, half-pot=25%) and noting that implied_extra lowers the required equity, adding cross-parameter meaning.

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 decision ('decide whether calling a bet is profitable') plus the exact outputs (pot odds, break-even equity, chance of hitting, verdict). It is clearly separable from analyze_hand (out counting) and calculate_equity (equity), so an agent can route without opening a schema.

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?

Explicitly tells the agent to use this instead of manual arithmetic, quantifies why (bet/(pot+bet) overstates the break-even share), explains when outs can be omitted (price only, no verdict), and names analyze_hand as the companion for out counts. When-to-use and the alternative are both covered.

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