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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered. The description adds useful context beyond that — the two rolling windows (30 and 7 days) and the link to a public hash chain proving results — but omits how the windows are computed, refresh cadence, and whether the sample is only settled calls (affecting denominators).

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?

A single front-loaded sentence with the substance first (hit rate, windows) followed by the provenance pointer and the access caveat. It is tight and free of filler, though the 'Members only' caveat would read better as its own short sentence than as a trailing fragment.

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-value explanation is not required, and with no parameters the calling mechanics are trivial. What the description still leaves open — authentication prerequisites and the settlement-window definition — is minor but relevant to an agent deciding whether it can call this at all.

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?

With zero parameters the baseline is 4; the description correctly signals that the tool takes no inputs and returns time-windowed aggregates rather than anything caller-specified. No additional param meaning is needed or offered, and none is possible.

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 states a specific resource and metric: aggregate hit rate for BitPredict members over 7- and 30-day windows, plus a hash-chain provenance pointer. It hints at sibling differentiation through the 'recently settled calls' framing and 'members' audience, but never names crowd_call, daily_call, or make_call to contrast the aggregate view with an individual or daily call.

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?

Usage is only implied: 'recently settled calls' and 'Members only' suggest reading performance after outcomes are known and that some membership/authentication context is required. There is no explicit when-to-use statement, no exclusion of alternatives, and no guidance on choosing this over the similarly named crowd_call or daily_call siblings.

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