check_business_exclusionsRun an exact UEI exclusion lookup for the connected business. This is not a compliance certification.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already disclose readOnlyHint, idempotentHint, and destructiveHint. The description adds the critical caveat 'This is not a compliance certification' and specifies the exactness of the lookup, which are meaningful behavioral details beyond the annotations. No contradiction with annotations.
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 concise sentences. The first sentence leads with the action and scope, and the second adds an important qualification. No redundant words, and the structure is front-loaded with the core purpose.
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?
The tool is simple, with no parameters and no output schema. The description explains the purpose, scope, and an important caveat. While it does not explicitly describe the return format, the nature of the tool makes the output predictable enough. Given the low complexity, this is adequate.
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?
The tool has zero parameters, so the schema trivially covers 100% of parameters. Per the baseline for 0 parameters, a score of 4 is appropriate. The description does not need to explain parameters since there are none.
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 states a specific action ('Run an exact UEI exclusion lookup') with a clear resource ('exclusion lookup') and scope ('for the connected business'). It also distinguishes itself from a general search tool by emphasizing 'exact UEI' and adds a disclaimer that it is not a compliance certification, which further clarifies its role relative to potential alternatives.
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 implies this is for the connected business and uses an exact UEI lookup, but it does not explicitly state when to use this tool versus siblings like search_exclusions or get_business_profile. There is no mention of scenarios where this tool should be preferred or when to use alternatives, leaving the agent to infer usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have clear boundaries (e.g., get_award vs search_awards, get_business_profile vs get_vendor). Some overlap exists in pairs like find_recompetes/find_recompetes_for_business and search_opportunities/search_opportunities_for_business, though the latter are differentiated by profile context.
All tools follow a consistent verb_noun snake_case pattern (get_, search_, update_, watch_, save_, etc.) with no stylistic deviations. Naming is highly predictable across the entire set.
At 39 tools, the surface is excessively large. While the domain is broad, many tools could be combined or parameterized (e.g., get_business_awards and get_vendor_awards, multiple search variants). This creates overhead for agents and dilutes focus.
The tool set covers the core lifecycle: opportunity/award searching and retrieval, business profile updates, saved searches, watches, exclusions, and reference data. Minor gaps such as award amendments or more granular exclusion handling exist, but the surface is fundamentally complete.