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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so 'Read-only' merely repeats structured data. What the description does add is the shape of the returned records (per-epoch fee split components and burn events with hashes). It says nothing about ordering, pagination, or how the limit governs results, so the addition is real but partial.

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?

One sentence, front-loaded with the data scope and the transaction-hash detail, with no filler. The closing 'Read-only' is the only wasted clause since annotations already assert 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?

There is no output schema, so the description shoulders the burden of describing returns; it does so at a high level by listing the record types and the hash field. However, for a paginated list tool it omits result ordering, whether the limit applies to fee splits and burns jointly or separately, and any indication of volume, leaving an agent unable to predict the response shape precisely.

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?

Schema description coverage is 0% and the single 'limit' parameter (default 20, max 100, min 1) is never mentioned in the description. With the schema carrying no textual semantics, the description needed to explain what the limit caps and in what order results are returned, and it does not. This is the clearest gap in the definition.

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 concrete resource: fee splits per epoch (WETH to stakers, buyback, operations) plus $KYTE buyback burns, each with a transaction hash. That is specific enough for an agent to distinguish it from neighbors like get_rewards or get_protocol_stats. The verb is only implied ('every ... each with its transaction hash') rather than stated, which keeps it just under a 5.

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 choose this tool over get_rewards, get_activity, or get_protocol_stats, and no prerequisites or exclusions. The trailing 'Read-only' is a safety note rather than usage guidance. The agent must infer the audit/verification use case from the data listed.

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