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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds context about what the tool contains (rules, strategy, call loop) but not additional behavioral traits like output length, formatting, or any runtime caveats. This is adequate but not rich; no contradiction with annotations.

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, front-loaded sentence beginning with 'START HERE,' followed by exactly the information an agent needs: game context, what the rules include, and why to read them. Every word earns its place; there is no filler or redundant repetition of the title.

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 zero-parameter, read-only, no-output-schema tool, the description is complete enough for correct invocation. It tells the agent this is the starting point, what content will be provided, and that it contains the recommended call loop. Nothing essential is missing for an agent to select and call it appropriately.

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?

The input schema has zero parameters, so there are no parameter semantics to document. Schema description coverage is 100% by nature, and the description does not need to compensate for anything. This is the baseline 4 for a no-parameter tool.

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 clear purpose: read the game rules and get guidance on how to play well, plus the recommended call loop. The 'START HERE' framing and game title ('Who's the Undercover') make it distinct from the action-oriented siblings (bluffo_act, bluffo_play, etc.). An agent can immediately recognize this as the entry-point reference tool.

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?

'START HERE' explicitly signals that this tool should be called first, before using sibling tools. The description also points to a 'recommended call loop,' giving the agent a reason to read it before acting. It does not explicitly name alternatives or state when not to use it, but the zero-parameter rules-reader role makes that exclusion fairly obvious.

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