calculate_pot_odds_and_mdf

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

No annotations are supplied, so the description carries the full behavioral burden. It does signal that results are deterministic closed-form computations ('exact'), which implies a pure, side-effect-free calculation, but it never says whether all five metrics are returned together or conditionally, nor how 'outs' interacts with the hypergeometric outputs. For a read-only calculator the risk is low, but the disclosure is thin rather than absent.

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?

A single front-loaded sentence with the verb first and the output set enumerated, with no filler or restatement. It is dense but every clause names a distinct deliverable; readability suffers slightly from packing five metrics into one sentence.

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?

For a three-optional-parameter, side-effect-free calculator with full schema coverage and no output schema, the definition covers what is computed but not the shape of the result or how outs=0 or outs>20 edge cases behave. Adequate to invoke correctly, but the agent cannot fully anticipate the response.

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 bet, pot, and outs are already fully documented with defaults and ranges; baseline is 3. The description adds only marginal semantic linkage, hinting that 'outs' drives the 1-card/2-card hypergeometric results and that bet/pot feed the odds and MDF math, but it gives no units (chips vs. big blinds vs. percent) or formula conventions.

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?

Opens with a specific verb ('Calculate') and enumerates the concrete quantities produced: pot odds ratio, break-even calling equity, MDF, polarized river bluff ratio, and hypergeometric draw completion. This is far more specific than a tautology and lets an agent tell it apart from calculate_poker_odds by the MDF/bluff-ratio/draw-probability outputs. It stops short of naming or contrasting that sibling, so a 4 rather than a 5.

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 when-to-use or when-not-to-use guidance, no mention of the closely named calculate_poker_odds sibling, and no stated preconditions. The agent must infer from the output list alone which calculator fits a given question, which is risky when a near-identical sibling exists.

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