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

Beyond the readOnlyHint and non-destructive annotations, the description adds meaningful behavior: it fans in multiple sub-sources, degrades per-section on unavailable sources rather than failing the whole call, and reports list_version for each screening source. It also discloses the $3.00 USDC cost. It does not detail output shape or auth, but the annotations already cover the safety profile.

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 compact and front-loaded with the use case, then the integration behavior, then the required input and price. It earns its place, though the phrase 'Fans in' is jargon-adjacent and slightly awkward, and the optional parameters are omitted rather than summarized.

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 complex fan-in tool with no output schema, the description gives a usable basic picture but leaves important gaps: what the composite dossier actually contains or how sections are structured, what optional parameters do, and what 'signed' means. It is minimally viable for calling with entity_name only, but not fully complete for an agent deciding how to use optional inputs or interpret the result.

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 0%, so the description must carry the parameter-documentation burden. It mentions only entity_name as required, repeating the schema, and leaves npi, state, industry, entity_type, and company_size completely unexplained. The sub-source list hints that npi relates to NPI verification, but there is no meaningful guidance for the other five optional 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 the exact resource and action: producing a signed composite vendor-onboarding dossier. It also distinguishes itself from the many single-source sibling tools by listing the specific sub-sources it fans in (OFAC, OIG LEIE, SAM, NPI, market rate, contract intelligence). The use case is front-loaded and 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 clear trigger: use when onboarding a vendor or counterparty and one composite examiner-facing dossier is needed. It does not explicitly say 'use the single-source siblings instead when you only need one check', but the fan-in description and the naming of source tools make that alternative reasonably inferable.

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