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

Beyond the annotations (read-only, idempotent), it discloses ingest-time behavior (addresses, SSN/TIN/NPI, and free-text comments dropped), filter combination logic (AND), the broad-search parameter, and a cost model including the unauthenticated preview cap of 5 rows/20 calls per day. These are precisely the operational facts an agent needs before calling.

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?

One dense but well-ordered paragraph that front-loads what the dataset is, then normalization guarantees, then filter semantics, then cost. No filler sentences, though the run-on structure requires careful reading.

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?

For a read-only search tool with no output schema and annotations covering safety, the coverage of sourcing, normalization, filter logic, and pricing is good. However the parameter surface is largely unexplained, leaving a meaningful gap for a 15-parameter filter 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?

With 15 parameters and 0% schema description coverage, the description carries the full burden, yet it only explains 'q searches all text fields' and that filters combine with AND. Key filters such as uei_sam, cage_code, classification, exclusion_type, and the four date bounds are left undocumented in both schema and description.

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+resource+scope: 'Every active exclusion (debarment) on the official US SAM.gov list', enumerating entity types (individuals, firms, special entities, vessels) and fields returned. This is unambiguously distinct from the many query_uk_* and query_eu_ted siblings.

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?

Frames the use case clearly ('normalized for supplier due diligence', 'served for compliance purposes'), which tells an agent when this belongs in a workflow. It stops short of explicit when-not guidance or naming an alternative source, but there is no direct sibling covering the same jurisdiction.

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