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

Annotations already cover read-only, idempotent, closed-world behavior, and the description goes further by disclosing how the estimate is derived (median of per-Agent median reward across the last 3 paid closes) and its fallback when the current segment has none. It does not state freshness/caching or precision of the estimate, so it is strong but not exhaustive.

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 core payload is packed into one long run-on sentence with a deep parenthetical about estimation methodology, which makes the important qualifier harder to extract than it should be. Length is reasonable, but the ordering buries the estimate caveat inside the field list rather than front-loading it.

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, the description usefully enumerates the returned fields, and it explains the estimate flag and fallback segment logic, which an agent needs to interpret the numbers. Missing details such as units for pool/reward and the shape of the per-close eligible-vs-paid data keep it just under full completeness.

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?

There is a single optional `segment` parameter with 100% schema description coverage, including the genesis-cut caveat and epoch-number repetition, so the schema carries all the semantics. The description never mentions `segment` or what the default (current segment) means for the numbers returned, so it adds nothing beyond the schema; baseline 3 applies.

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 specific resource (the payout outlook for the next close) and enumerates its contents: per-Agent estimate, basis closes, next close epoch/time, pool, answered/K-attested Agents, and eligible-vs-paid per close. That enumeration separates it from siblings like get_current_epoch or get_epoch_record, though no sibling is named explicitly.

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?

"Use it before the next close to see what an Agent may earn" gives a clear usage window, and the note that the figure is an estimate until the close record lands implies when to stop using it. It stops short of naming the alternative tool (e.g. the epoch/close record endpoint) for post-close reads.

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