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

Annotations already declare readOnlyHint=true and openWorldHint=false; the description reinforces read-only behavior and adds a genuinely useful negative disclosure — that names, credentials, invitations and cards are never returned. That data-exposure boundary is context the annotations do not carry, though error behavior for a missing or invalid table_id is not disclosed.

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?

Two short sentences, front-loaded with the read-only scope and the returned fields, then the non-returned data. No filler, no restatement of the tool name.

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 one-parameter read tool with annotations and no output schema, the description covers the important ground: it is read-only, it returns status and seats, and it explicitly excludes sensitive fields. Only the identifier's meaning and failure behavior are missing, which is a minor gap at this complexity.

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 single parameter, table_id, is never mentioned in the description. The schema does supply format=uuid and a UUID pattern, so the value shape is machine-discoverable, but the description adds nothing about what the ID refers to (table vs game vs invite) or how a malformed/unknown ID is handled.

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 states a specific read operation and enumerates exactly what is exposed: existence, waiting/in-progress state, and available seats. It is clear what the tool returns, but it never names or contrasts the sibling tools (get_game_info, get_play_link), so a routing decision still requires inference.

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?

Usage is only implied: an agent can infer this is the lightweight status check, but the description never says when to call it versus get_game_info or get_play_link, nor does it state any precondition such as the table already existing. No exclusions or alternatives are given.

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