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

Annotations already declare readOnly/not destructive/closed-world, so the safety profile is covered structurally. The description adds little behavioral context beyond the output shape, and that shape is partly covered by the content it names. It doesn't mention determinism, whether analysis changes with board count, or limits.

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 front-loaded sentence that names the operation and its outputs compactly. Efficient, though the return enumeration slightly overlaps with what an output schema would carry.

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?

Adequate for a two-param read-only analyzer: schema and annotations carry safety and input semantics. With no output schema, the description must convey return shape, and it names the return pieces (category, label, draw out counts) but doesn't describe the structure or field names.

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% and both params are documented with examples ('Jh Th', '9h 8h 2c'), so the baseline is 3. The description restates the board range (3-5 cards) but adds no format or syntax beyond the schema.

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 verb (Read/analyze), resource (one Texas Hold'em hand), and exactly what it returns: made hand category/label plus every draw with its out count. Clearly distinct from calculate_equity and calculate_pot_odds, which handle equity and pot odds rather than hand strength.

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 implies when to use it (evaluating a hand on a 3-5 card board), but never explicitly names calculate_equity or calculate_pot_odds as alternatives or states when-not to use it. Usage is inferrable but not spelled out.

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