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

readOnlyHint=true already declares the safety profile, so the bar is lower; the description adds that the record is public and mirrors the results page exactly, and defines the 'void' term. The remaining sentences (21+, no wins promised, does not take bets) are legal disclaimers rather than invocation-relevant behavior such as scope, freshness, or aggregation level.

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 useful content is one front-loaded sentence; the following three sentences are compliance boilerplate that does not help an agent select or invoke the tool. Roughly half the description is spent on text that earns no place in a tool definition.

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 output schema and no parameters, the description does the right thing by describing the returned fields, which is necessary here. But it leaves unclear whether this is a single aggregate record or per-pick history, and gives no hint about refresh cadence or how it differs from get_results.

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 the baseline is 4; there is nothing parameter-related the description needs to compensate for. Schema coverage is 100% and the empty object confirms no input is required.

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 names the resource and enumerates its contents (wins, losses, voids, current streak, date range) and clarifies that a void is a push or no pick, so an agent knows what data comes back. It does not, however, distinguish this from the sibling get_results, which by name appears to return overlapping results data.

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?

There is no statement of when to call this versus get_results or verify_pick, and no preconditions or exclusions. The only usage-adjacent text is the 21+ / entertainment disclaimer, which does not help an agent choose between tools.

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