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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It clearly explains the unified deduped check across multiple sources, the return types (match/possible-match/no-match), matched record details, and confidence score. It also explicitly states it is not a consumer report. This provides good transparency despite lacking rate limits or authentication details.

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 concise: three sentences that front-load the core purpose, list key databases, explain return values, and add a critical legal disclaimer (FCRA-safe). No wasted words, and the structure is clear and scannable.

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?

Despite no output schema, the description adequately covers return values (match types, matched records, confidence score). It explains the scope (federal and state exclusions) and deduped nature. Missing details like pagination or example confidence thresholds, but overall fairly complete for this tool's complexity.

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 100%, so the baseline is 3. The tool description does not add extra parameter semantics beyond the schema's own descriptions (e.g., NPI for LEIE, state for disambiguation). The schema descriptions are already informative, so the description adds minimal additional value. Score 3 is appropriate.

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 clearly states it screens business entities for federal exclusions and sanctions, listing specific databases (OFAC, HHS-OIG, SAM.gov, state lists). It differentiates itself from siblings like screen_batch (batch) and watch_entity (ongoing) by focusing on pre-onboarding/payment checks. The purpose is precise 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?

The description indicates when to use ('before you onboard or pay it') and clarifies it's for entities only (FCRA-safe for KYB). However, it does not explicitly state when not to use this tool (e.g., for individual checks or ongoing monitoring) or compare with sibling tools. The guidance is adequate but lacks exclusions.

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