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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so 'Read-only' in the description is largely redundant. What the description does add beyond structured fields is substantive: the interpretive caveat that a rank is not a verification, and the disclosure that entries carry a research status and low-sample flag worth scrutinizing.

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 purpose is front-loaded in the first clause, followed by the field inventory and then two short qualifying sentences. It is dense but every clause carries content (window scope, flags, the rank-vs-verification caveat); 'Read-only' is the one redundant fragment already covered by annotations.

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 and the tool takes no parameters, so the description only needs to frame what the returned ranking means and how to interpret it. It does this, including the crucial 'rank is not verification' framing and the low-sample flag, leaving nothing an agent needs missing before calling it.

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?

Zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly avoids inventing parameter-like details for a no-argument tool.

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 (get) and resource (PRUVIQ's published daily ranking snapshot), then enumerates the contents: best/worst strategy configurations by backtest over the published window, research status, sample size, low-sample flag, and headline note. This is enough for an agent to distinguish it from siblings like get_coin_strategy_stats or get_forward_verification_records.

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 implied rather than stated: 'daily ranking snapshot' and 'published window' suggest when the data applies, and the caveat 'A rank is not a verification' implicitly routes verification questions to siblings like get_forward_verification_records or get_strategy_verdict. However, no alternative is named and no explicit when-to-use / when-not-to-use condition is given.

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