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

Annotations already establish readOnly, idempotent, non-destructive, and closed-world. The description adds genuinely new behavioral context beyond them: data is served 'from a stored copy' with read_at indicating staleness, and the 'live' flag communicates whether on-chain state has been written yet. That staleness/state caveat is the kind of disclosure annotations cannot carry.

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 length is defensible because no output schema exists, so the return-field enumeration earns its place. However, it is delivered as one long run-on sentence stringing status values, signing cadence, settlement rules, and account details together, which impedes front-loaded scanning after the first clause.

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 carries the full burden of explaining return values and does so thoroughly (per-index value, period, status, cadence, settlement eligibility, read threshold, rule version/hash, Solana account). Combined with the staleness note and the get_report fallback, an agent has enough to call and interpret the tool, though the settling-rule and status enumerations remain terse.

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 declares zero parameters at 100% coverage, so there is nothing parameter-level for the description to compensate for. Baseline 4 applies; the description correctly does not invent or describe inputs, and instead spends its words on the response shape.

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 opening clause states a clear verb and resource ('every Tickerz oracle feed at once'), and the tool is distinguishable from get_report, which is named as the alternative for scenarios where the Solana program is not yet live. The bulk of the description enumerates return fields, which is output detail rather than purpose, but the core purpose is unambiguous.

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?

It gives an explicit trigger ('when a contract, a venue or a person wants every feed at once') and names a concrete alternative with a condition: when 'live' is false, read signed reports via get_report instead. It stops short of covering other sibling tools (get_index, list_indices) that an agent might weigh, but the primary routing decision is spelled out.

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