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

Annotations already declare readOnly=false, idempotent=false, destructive=false, openWorld=false; the description adds the crucial consequence that each call creates a NEW table and that links should be reused, which explains the non-idempotency in practical terms. It does not say what happens to abandoned tables or whether links expire.

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?

Three short sentences, front-loaded with the core action, and the reuse rule is placed after the action it constrains. Slightly padded by 'Supports bots or friends', which only partly duplicates the opponents enum.

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?

With 5 optional parameters and no output schema, the description should explain what player_name and bot_count mean and that only omaha_hi_lo tables can be created. It also omits what the returned link looks like or how long it is valid, so an agent must inspect the schema and still guess.

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% across 5 parameters, so the description carries the full burden. It only obliquely covers 'opponents' via 'bots or friends'; private, bot_count, player_name, and the fixed omaha_hi_lo game_type are never mentioned, leaving most parameters undocumented anywhere.

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+resource combination: prepares a NEW playable table and returns its join link, which clarifies that despite the 'get_' name this is a creating action. It does not mention or differentiate from the sibling create_poker_table, so an agent must guess which creation path to take.

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?

'Reuse a previously returned link instead of calling again when possible' is an explicit when-not-to-call rule, which is exactly the guidance an agent needs for a non-idempotent tool. It stops short of naming alternatives or stating prerequisites, so it is clear but not complete routing guidance.

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