Check Exclusion

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

The description discloses that it returns matching exclusion records with reason, agency, and dates. It aligns with readOnlyHint and idempotentHint, adding behavioral detail beyond annotations without contradiction.

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, well-organized with bullet points for parameters, and uses clear, direct language without redundant information.

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?

Provides comprehensive guidance: what it does, when to use, required input, and the nature of the output. The presence of an output schema means detailed return fields need not be enumerated.

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 description explains the meaning of three parameters (name, uei, cage_code) but omits the 'limit' parameter, which is present in the schema with a default. Coverage is high but not complete.

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 the tool checks the SAM.gov exclusions list (debarred/suspended entities) and distinguishes it from sibling search tools by its specific exclusion-checking purpose.

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?

Explicitly states when to use ('before subcontracting or teaming, and again periodically post-award') and provides a precondition ('Provide at least one of: name, uei, cage_code').

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