sam_search_opportunities

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

With no annotations, the description provides key traits: returns up to 50 active notices, keyless (no authentication). Lacks disclosure of rate limits, data freshness, or behavior for empty results.

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 defines function and output, second gives usage guidance. No redundant phrasing, every word earns its place.

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 essential return fields and a default limit of 50, adequate for a discovery tool. Could mention sorting or lack of pagination, but overall sufficient given no output schema.

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 covers 83% of parameters. Description adds value by directing users to sam_lookup_organization or usas_lookup_agency for resolving abbreviations in organizationName, and lists setAside codes, exceeding schema details.

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?

Clearly states the tool searches SAM.gov federal contracting opportunities, specifies return fields (title, agency, NAICS, noticeId), and notes the 'keyless HAL' public access. Distinguishes from sibling tools like sam_get_opportunity as a discovery tool.

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 says 'Use for discovery' and suggests narrowing strategies (NAICS, agency, set-aside, state). Implicitly indicates when not to use (for details), but does not name specific alternative tools like sam_get_opportunity.

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