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

No annotations are supplied, so the description carries the burden, and it does disclose the shape of the result (two named lists). It does not state that this is a read-only listing, whether results are paginated or filtered, or what ordering applies — a meaningful gap for a tool with zero annotation coverage.

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 no filler; the two returned lists are named efficiently. It errs toward terseness rather than verbosity, but nothing in it is wasted.

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 low-complexity, two-parameter tool with no output schema, the description usefully explains what comes back. However, it leaves the status filter unexplained and says nothing about the auth expectations beyond what the api_key schema field already states, so it is adequate but not complete.

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 only 50% (api_key documented, status undocumented), so the description should compensate — but it never mentions the status parameter or what current/all/finished mean. The agent must guess the default and the scope of each enum value from the bare 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?

The description states the resource clearly (your liar's dice tables) and even enumerates the two collections returned (your_turn_in, invites_for_you), which distinguishes it from dice_get_game and dice_play. It lacks an explicit verb like 'list', but the intent is unambiguous.

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?

It implies the moment to use it (finding where you need to act and where you've been invited), which is genuine usage context. It gives no explicit alternative or exclusion, such as using chess_my_games for chess tables or dice_get_game for a single table's detail.

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