govinfo_list_collections

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

The description adds significant behavioral context beyond the 'readOnlyHint' and 'openWorldHint' annotations, including memoization (6h), details on count semantics (null vs 0 for granuleCount), and its role as validator source for search_packages. No contradictions with annotations.

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 concise and front-loads the purpose, output structure, and usage hints. It packs multiple pieces of information into a single paragraph without redundancy, though it could be slightly more structured for readability.

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?

Given the tool's simplicity (no params, no output schema), the description fully covers the output format, memoization, edge cases (null counts), and integration with sibling tools, making it complete for an AI agent to use correctly.

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?

With zero parameters and 100% schema coverage (empty schema), the description correctly adds no parameter details. The baseline for zero-param tools is 4, and the description focuses on output and usage, which is appropriate.

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 clearly states it lists the GovInfo collection catalog and distinguishes itself from sibling tools like 'govinfo_search_packages' by noting it is the discovery entry-point that provides collection codes for further searches.

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 states 'No input' and positions itself as the starting point for using 'govinfo_search_packages', providing clear usage context. However, it does not explicitly list conditions where it should not be used, though its simplicity makes this less necessary.

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