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

No annotations exist, so the description carries the full burden. 'Frozen' usefully signals a precomputed/static forecast and 'no paid dive' signals no cost or premium gating, but it says nothing about error behavior for unknown slugs, determinism, or what the response contains.

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?

One tight sentence with the core operation front-loaded and zero filler. The 'no paid dive' clause is compact but cryptic enough to cost some clarity.

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 one-param read tool with no annotations and no output schema, the essential 'what it does' is present. Missing details on return shape, staleness semantics of 'frozen', and failure modes leave it merely adequate.

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 single parameter has 0% schema description coverage, so the description must compensate. It adds the useful qualifier that the slug refers to a 'public game', but does not clarify slug format, source (e.g., matchup ID vs. week slug), or validation rules.

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?

Specific verb ('Read') plus resource ('frozen Elo forecast') scoped to a 'public game slug'. It implicitly differentiates from the sibling get_member_dive via 'no paid dive', though the phrasing is jargon-laden rather than a clean contrast.

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 phrase 'no paid dive' hints that this is the free counterpart to a paid tool, but it never names get_member_dive or states the selection condition explicitly. 'Public game slug' implies a restriction to public games, but no exclusions or alternatives are spelled out.

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