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

With no annotations, the description carries the full burden and does reasonably well: it discloses the return shape (hits naming the door, id or page to buy, fetchedAt/asOf), the pricing model, and explicit exclusions (no letter/decision/order bodies, no full import-alert table). It omits auth requirements, rate limits, or pagination behavior, keeping it short of a 5.

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 free-search claim, return shape, and pricing are front-loaded, which is good, but the 24-item enumeration of source caches is bulky and largely restates sibling tool names. It earns partial value by conveying coverage scope, but a summary would communicate the same 'cross-door' idea more cheaply.

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 annotations, so the description must carry the return format, cost, and limitations itself — and it does all three. For a single-parameter search tool this is close to complete; only auth and pagination/result-count details are missing.

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% and the single 'q' parameter is fully documented in the schema (firm/institution/bank/company/FEI/CMS/import-alert number, free). The description adds no syntax or matching-behavior detail beyond that, so the baseline of 3 applies.

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 opens with a clear verb+resource ('cross-door search of official caches') and then enumerates precisely which caches it spans, so an agent can tell it is a union search over many sibling sources rather than a single-door tool. The signal is diluted by the long source list, but the core purpose is unambiguous.

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 states the search is free and that fetching actual texts costs $0.02 (GET ?id=) or $0.05 (newest-10 page / import-alert table), which implies the search-then-buy workflow. However, it never explicitly routes the agent between this and sibling tools like 'search', 'get-one', or 'get-page', leaving selection to inference.

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