sam_search_opportunities

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

No annotations provided, so the description must carry the full burden. It mentions 'keyless HAL' (suggesting no API key needed) and a limit of 50 active notices, but does not clarify authentication requirements, rate limits, or the scope of 'active' (e.g., ongoing vs. upcoming). Adequate but could be more transparent.

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 with no wasted words. Front-loaded with the core action and result, then provides refinement hints. Exceptionally concise while remaining informative.

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?

Given the lack of output schema, the description adequately covers the tool's purpose, output fields, filtering options, and behavior (up to 50 results). Siblings exist but the tool's role as a broad search is clear. Could benefit from noting that it only returns active opportunities and not historical data, but overall complete for a discovery tool.

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 high (83%) and the input schema already describes all parameters except limit. The description adds minimal extra semantic value beyond repeating the parameter categories (NAICS, agency, etc.) and providing a list of set-aside codes. Baseline of 3 is appropriate.

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 it searches SAM.gov federal contracting opportunities and specifies the key output fields (title, agency, NAICS, noticeId) and usage for discovery. However, it does not explicitly distinguish itself from sibling tools like sam_get_opportunity or sam_lookup_organization, which could refine the 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?

Provides explicit guidance to use the tool for discovery and to narrow results by NAICS, agency, set-aside, or state. Lacks explicit when-not-to-use or direct comparison to sibling tools, but the guidance is clear and actionable.

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