SAM.gov Entity Detail

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds what data is returned (legal name, CAGE code, etc.) and the source, but does not provide additional behavioral traits beyond these 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 sentences: first states purpose, second lists key returns. No unnecessary words, front-loaded with verb and resource. Highly efficient.

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 single-entity lookup tool with an output schema (not shown but stated), the description covers essential return fields and source. No missing context like pagination or errors needed for this simple query.

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 coverage is 100% with one parameter fully described, including an example. The description adds context by explaining the UEI and providing an example (e.g., 'KM99JJBNQ9M5 for Lockheed Martin'), adding value beyond the 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?

The description clearly states the tool retrieves full SAM.gov registration details for a federal contractor by UEI, listing specific returned fields. This distinguishes it from the sibling 'sam.gov.entity_search' tool, which likely searches for entities rather than returning full details for a known identifier.

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 implicitly indicates usage when a UEI is available, but does not explicitly mention when to use or not use alternatives like sam.gov.entity_search. The context is clear, but explicit exclusions are lacking.

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