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

Annotations already cover read-only, idempotent, open-world, and non-destructive behavior, and the description adds real substance on top: size caps (4 MiB vs 1 MiB), that packets can be partial, that restricted sources may withhold values, that source JSON is untrusted, and that no Evidence Carrier verification occurs. Its weakness is opaque jargon ('publication projection receipt', 'dependent readings') that an agent cannot act on without further context.

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 purpose is front-loaded in sentence one, but the remaining four sentences compress many distinct caveats into dense, jargon-heavy clauses ('publication projection receipt and a separate hash from the acquired source bytes'). Informative but hard to parse on a single read.

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 and no description of what a packet actually contains or how partiality manifests, and the sole parameter is undocumented. Size limits and trust caveats are present, but an agent still cannot predict the response shape or select topics 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% and there is only one parameter, yet the description says nothing about 'topics' — what a topic selects, whether multiple topics may be combined, or how the five enum values (money-market, china-economy, etc.) differ. With no schema documentation to fall back on, this is a notable gap.

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 first sentence states a specific verb and resource ('Retrieve public documents') and adds a scope condition ('only when table detail is insufficient'). It never names any of the eight sibling tools, so the distinction from financial_evidence_query or financial_evidence_sources must be inferred from the vague phrase 'table detail'.

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?

'Retrieve public documents only when table detail is insufficient' gives a clear gating condition for use, implying that tabular/aggregate tools come first. However, no alternative is named and no explicit case is listed where the tool should not be used, leaving the agent to guess which sibling supplies the 'table detail'.

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