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

Annotations already establish this as a safe read-only, idempotent, closed-world operation, and the description adds substantial behavioral detail: ordering, count, age, stale flag, histogram buckets, expiry timing, settlement origin, growth anomalies, and silent drops. This is rich disclosure beyond structured metadata.

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 content is dense but front-loaded: first the definition of the backlog, then the return fields, then usage routing. The first sentence is long and list-heavy, which slightly reduces readability, but every item appears purposeful.

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 parameters, no output schema, and read-only annotations, the description supplies everything needed: what it returns, how results are grouped and ordered, the anomaly fields, and when to choose alternatives. Nothing material is missing for correct invocation.

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 are no input parameters, so the baseline is 4. The description rightly does not invent parameter semantics, and no parameter guidance is needed.

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 a specific resource (pending/ungraded answers) and a specific grouping (by epoch, oldest first), and contrasts it with sibling tools for related queries. An agent can distinguish it immediately from get_epoch and get_answer_receipt.

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 explicitly says to use this tool for backlog and queue questions, then names two alternatives for adjacent use cases: get_epoch for one epoch's answers over time and get_answer_receipt for a single answer. That is clear routing guidance.

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