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

The annotations already declare read-only, idempotent, closed-world, and non-destructive behavior. The description adds some valuable caveats, notably "No summary pagination" and "Retrieval age is not observation freshness," but it does not explain what rights/clocks data means or how results are shaped.

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 description is short and has no obvious filler, but it is telegraphic and fragmented rather than clearly structured. The information is compact yet under-explained, which hurts usability more than length does.

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, zero schema description coverage, and the description leaves view semantics and return fields largely unexplained. For a metadata/context tool with three parameters, this is not enough for an agent to invoke it confidently.

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%, so the description must carry parameter meaning, but it only vaguely connects pagination to summary views and mentions records/total/next_offset. It does not explain the view enum values or the limit/offset behavior for non-summary views.

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 is a noun-phrase fragment, "Corpus coverage/rights/clocks," and does not state a clear operation or what an agent should expect back. It is not pure tautology, but it is too vague to confidently distinguish the tool from siblings.

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 hints that summary views do not paginate and mentions other views, but gives no explicit when-to-use guidance, prerequisites, or alternatives among the many sibling tools. The "Readings: liquidity_tiers" fragment is especially opaque as usage direction.

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