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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful context about the data source and what kind of records are searched, but says nothing about match behavior (exact vs fuzzy), whether only currently active exclusions are covered, or what the result looks like.

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?

A single well-formed sentence with the verb, source and scope front-loaded and the technical terms glossed inline. No filler and nothing that could be cut.

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?

With rich annotations, full schema coverage and no output schema to explain, the description covers the essentials an agent needs to invoke it. What is missing is routing versus screen_sanctions and any note on result interpretation, which keeps it short of complete.

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 both the 'name' and 'subject_type' parameters are already documented, including the default heuristic for subject_type. The description adds no formatting guidance for the name (e.g., legal suffix or middle-name handling), so it stays at the baseline for a fully documented schema.

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 ('Check') and resource ('a name against SAM.gov federal contracting exclusions') and even unpacks the jargon with '(debarments/suspensions)'. It does not, however, differentiate itself from the closely related sibling screen_sanctions, leaving the agent to guess which screening source applies.

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?

There is no when-to-use or when-not-to-use guidance. The description never mentions screen_sanctions or any other sibling, so an agent cannot tell from this text when federal exclusion screening is preferred over sanctions screening or a full due_diligence_report.

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