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

Annotations already cover readOnly, idempotent and non-destructive, so the safety profile is settled elsewhere. What the description adds is real behavioral value: the exact shape of the payload and the default semantics of omitting epoch, which annotations cannot express.

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?

Two sentences, zero filler, with the substantive payload description first and the invocation shortcut second. Nothing repeats the title or 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?

With no output schema, listing the returned fields is exactly what is needed and it is done. Minor gaps remain — behavior for an out-of-range or future epoch, and the top_rewards control — but an agent could call this correctly as written.

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 coverage is 0%, so the description must carry the parameters. It clarifies 'epoch' (omit = latest close) but says nothing about top_rewards — its default of 10, its 1–200 bounds, or that it controls how many rewards are returned instead of being a response field. Half the parameters remain undocumented.

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?

Names a specific resource (one closed epoch) and enumerates what it returns — pool, minted, burned, paid agents, grading stats, top rewards — so the agent knows this is a detail fetch, not a list. It is distinguishable from get_current_epoch by the word 'closed', though the 'latest close' default muddies that boundary slightly.

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?

Gives one usable procedural rule ('omit epoch for the latest close') but never states when to prefer this over the sibling get_current_epoch, which is the obvious alternative an agent will weigh. Usage is implied rather than explained.

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