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

No annotations are provided, so the description carries the full burden. It discloses ordering ('newest first') and the exact contents of a hand (board, log, showdown, rake, seed), which is useful. However, it does not state whether the operation is read-only, any authorization requirements, or pagination behavior. Since it appears to be a simple query, the lack of side-effect disclosure is not critical, but more behavioral context (e.g., rate limits) would be better.

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 a single, information-dense sentence with no fluff. It front-loads the core purpose and lists the data components efficiently. It is concise without being under-specified, though it could benefit from a brief mention of the limit parameter.

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?

Given no output schema and 0% parameter coverage, the description should compensate by explaining the parameters and the response shape. It only hints at the data fields but does not explain 'seed' or how 'limit' affects results. An agent would not know what to expect in the response or how to use the limit parameter, leaving it incomplete.

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 0%, and the description does not mention either parameter. 'tableId' is inferable from context, but 'limit' is completely unexplained (its type, purpose, default, or constraints). The description adds zero value for parameter understanding, forcing the agent to guess.

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 clearly states the tool retrieves hands dealt by a specific table, listing components (board, log, showdown, rake, seed) and ordering (newest first). This is distinct from siblings like poker_tables (which lists tables) and poker_act (which takes actions), so an agent can identify it without ambiguity.

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 usage (when you need hand history for a table) by specifying what it returns, but it does not explicitly mention alternatives or when not to use it. Given the surrounding siblings, the context is clear enough, though explicit routing would improve it.

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