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

Annotations only cover read-only/idempotent/closed-world, but the description adds substantial behavior: cursor results are 'pinned windows' that ignore or repeat the original topic/filter, oversized values must be fetched back through this same tool via record_handle + record_path, and countries mix LDA codes with non-ISO FARA source labels that are explicitly not normalized. These are exactly the non-obvious traits an agent would otherwise get wrong.

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?

Four front-loaded sentences, each carrying distinct information (scope, filter semantics, paging/overflow mechanics, data caveat) with no filler. Density is high but justified; a slightly clearer split between the list vs. explain modes would improve scanability.

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 an output schema present, return shapes need not be explained. All seven parameters are fully documented in-schema, and the description closes the remaining gaps (continuation semantics, overflow retrieval, country-code caveat) for what is otherwise a fairly complex paging-plus-reference tool.

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 100%, so the baseline is 3; the description still adds relational meaning the schema does not spell out, namely that record_handle and record_path are used together on this tool to unpack oversized entries, and that cursor payloads override or repeat topic/filter. It does not add format detail for record_path (JSON Pointer) or record_offset, which the schema already carries.

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 verb (list / explain) and enumerates the exact resource set: issue codes, filing types, government entities, contribution types, countries, plus explanatory topics. This vocabulary-topic framing cleanly distinguishes it from all siblings, which are search/get tools over filings and agents.

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 gives clear operating context: filter is optional and does token-AND literal matching, cursors drive continuation, and record_handle/record_path are for oversized entries. It stops short of naming alternatives or stating when not to use it (e.g., use search_filings rather than this reference tool for record lookups).

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