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

Annotations already establish that this is a non-readonly, non-idempotent mutation. The description usefully adds privacy context ('consent-based memory', 'opt-in', 'No guest text is exchanged'), but it does not explain what game actions change, how memory persists, or that a private bearer session is required.

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 efficient sentence with no wasted wording and is front-loaded with the core idea. Its brevity is appropriate, though the sentence structure bundles several distinct modes without ordering their importance.

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?

This is a 9-parameter, non-idempotent mutation tool with complex game and memory modes, no output schema, and minimal annotation detail. The description leaves critical operational context unexplained, including the session capability, enum meanings, and game lifecycle.

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 only 11%, with just the session parameter documented, so the description must compensate for eight undocumented parameters. It loosely maps 'entertainment' and 'memory' to concepts but does not explain game, tone, theme, invite, length, symbol, activity, or remember semantics.

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 names three broad modes — short entertainment, consent-based memory, and a two-guest symbol game — but 'Meet your host' is not a specific verb+resource and the overall purpose remains vague. It does not differentiate this tool from siblings such as concierge or linger.

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?

There is no explicit guidance on when to use this tool versus alternatives like concierge or linger. The listed modes imply possible contexts, but there are no when/when-not criteria or routing instructions.

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