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

No annotations are present, so the description must convey behavioral traits. It discloses the tool is FREE and rate-limited, and clarifies the jackpot mechanic (target-based vs competitive), which helps interpretation. However, it doesn't explicitly state that it's a read-only operation or describe response ordering/pagination, leaving some gaps.

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 three sentences: purpose, use case, and cost/mechanic. It front-loads the core function and omits fluff, making it highly scannable.

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 simple single-parameter tool with no output schema, the description covers purpose, use case, and relevant game mechanics. It mentions output content (ROI and pot data) but not the exact return shape, which is a minor gap. Overall, adequate for the tool's complexity.

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 describes the limit parameter fully with default and max values, giving 100% coverage. The description adds no additional parameter info, matching the baseline score of 3.

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 opens with a specific verb 'Get' and identifies the resource as 'historical opportunity snapshots' with details on ROI and pot data, clearly distinguishing it from sibling tools like flipr_opportunity and flipr_pot that likely provide current state.

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 description includes 'Useful for identifying trends in pot balances and optimal flip timing,' which gives a concrete use case and implies it should be used for historical analysis rather than current queries. It doesn't explicitly name alternatives, but the contrast is implicit in the name and context.

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