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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety and side-effect profile is fully covered by structured data. The description adds nothing beyond that: no pagination behavior despite a cursor parameter, no rate-limit or result-shape context, and no note on how empty queries are handled.

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 single sentence is front-loaded and free of waste, which is good structure. However, at this length for a search tool with an undocumented free-text parameter, the brevity reads as under-specification rather than efficiency, so the sentence does not fully earn its place.

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 parameters, low schema coverage, and no explanation of the result shape or pagination loop, the definition leaves real gaps for an agent to call this correctly. It should at minimum describe what a returned collection looks like and how cursor/per_page interact.

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 only 33%; cursor is documented in the schema but q and per_page have no descriptions anywhere. The description does not compensate at all — it never says whether q matches collection titles, subjects, or full text, nor what per_page accepts or its limits, so an agent must guess at two of three parameters.

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 pair (list/search) and a specific resource (Library of Congress digital collections), so the agent knows the domain of results. It does not distinguish this from the sibling loc_search, which by name also appears to search LOC content, leaving the collections-vs-items boundary ambiguous.

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 when-to-use guidance, no when-not-to-use exclusions, and no reference to any alternative such as loc_search or loc_get_item. The phrase 'List or search' hints at two modes but never says which inputs select which mode or when an agent should prefer this over a sibling.

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