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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description does add real context beyond them: default responses return truncated metadata unless limit is raised, and the call has no side effects on identity, scores, or eligibility while retaining rights. It still omits pagination behavior for offset and what a result record contains.

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 tight sentences with no padding, but the brevity is achieved through opaque proper nouns rather than compressed clarity, so density does not translate into information for the caller.

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, three undocumented parameters, and a nine-value topic enum, the description should explain what comes back and how topic/offset behave. Instead it leaves the agent guessing about the result shape and pagination semantics.

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. It only hints at 'limit' controlling metadata completeness; topic (a 9-value enum) and offset are entirely unexplained, and it never clarifies whether limit counts records or metadata fields.

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 verb 'route to' is vague and the resources are four internal codenames (Palimpsest, Seiche, Undertow, NarcoScope) that an agent cannot map to a concrete operation. Nothing distinguishes it from siblings like universe_search, evidence_markets, or institution_research_coverage.

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 use this tool versus the many evidence_*/research_* siblings, no prerequisites, and no exclusions. The only actionable phrasing ('Set limit for full metadata') is a parameter note, not usage guidance.

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