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

With no annotations, the description carries the behavioral burden and does well by disclosing the key trait that hidden rolls never appear until the exchange resolves, plus that it is public and free. It omits auth requirements, behavior for finished matches, and any rate/refresh semantics for a 'live' view.

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?

Front-loads the [FREE] Public spectate framing and packs the return contents into one dense but readable clause before the replay fallback. Slightly long, but nearly every clause adds useful information.

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?

An output schema exists so return values needn't be spelled out, yet the description still summarizes what is visible, which helps. It is largely sufficient for a single-parameter read tool, with auth and match-state assumptions being the only notable omissions.

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 0% and the single match_id parameter is undocumented in the schema. The description references match_id only implicitly through the replay URL path and does not explain its format or where to obtain it, so it only partially compensates for the coverage gap.

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 and resource: a public spectate view of a live BLUFFDUEL dice duel, and enumerates the visible content (dice counts per seat, bid history, turn order, revealed rolls). An agent can immediately tell this apart from the bluffduel_queue/register siblings and from generic spectate views.

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?

Signals the live-observation context via 'live' and '[FREE] Public spectate', and points to a replay endpoint for full replays, which is a form of alternative routing. However it never states when to prefer this over the replay URL, prerequisites, or whether a match must be in progress.

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