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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety and external-dependency profile is fully covered structurally. The description adds only that filtering is optional, and says nothing about result volume, pagination behavior, or rate limits on the upstream loc.gov API.

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 short sentences with the core capability front-loaded and the filtering note immediately after. The trailing 'Served by Profullstack (https://...)' vendor line is boilerplate that adds no invocation value, keeping it from a 5.

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 five optional parameters, rich annotations, and no output schema, the definition is adequate but thin: it never explains that results are paginated via cursor, nor what a response contains. An agent can call it correctly from the schema alone, but the description does not fill the remaining gaps.

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 80%, so the baseline is 3 and the schema already documents q, cursor, per_page and collection. The description adds marginal value by giving example format values (photos, maps, books) and noting the collection argument is a slug, but does not explain the cursor/per_page paging contract in prose.

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?

States a specific verb and resource: 'Search Library of Congress digital collections on loc.gov', which tells an agent exactly what is queried. It does not differentiate itself from siblings like profullstack_loc_get_item or profullstack_loc_list_collections, so an agent must infer that this is the search/list endpoint versus the retrieval endpoint.

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?

The only guidance is optional filtering ('Optionally limit to a format... or a collection slug'), which is parameter usage rather than when-to-use-this-vs-alternatives. There is no statement about when to search versus when to fetch an item directly, though the search intent is strongly implied by the name and verb.

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