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

Annotations already declare this a safe, read-only, idempotent, non-open-world call, so the safety profile is covered. The description adds real context beyond that: the whistle read is deliberately a single word (busy/average/quiet), and the payload is a teaser with fuller reports living elsewhere. That tells an agent to expect coarse summaries and not to over-promise detail, which is useful behavioral framing.

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 sentences, zero padding. Content comes first (games, crews, rating, take) and the scope caveat plus external pointer follow, which is the right front-loading for an agent scanning tool lists.

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?

With no parameters and no output schema, the description carries the whole burden of explaining what comes back, and it does so at a reasonable level: games, crews, a categorical rating, and commentary. It is slightly thin on the shape of the response — e.g. whether every game has an assigned crew, or what 'Monty's take' actually contains — but nothing essential to calling it is missing.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline applies. The implicit meaning of that empty schema — always 'tonight', no date or team filter — is at least consistent with the description's framing.

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+resource combination: tonight's NBA games, each referee crew, a one-word whistle rating, and commentary. An agent can tell this is a nightly slate snapshot rather than a lookup, which is enough to separate it from nba_game_refs and nba_referee. It stops short of naming those siblings explicitly, so the differentiation is inferred rather than stated.

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?

The line 'Preview only: the full reports are on WhistleBets' signals when this is the right tool (a quick look) and where to send a user for depth. However, it never explicitly contrasts itself with nba_game_refs or nba_referee, so choosing between them is left to the agent's inference from the names.

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