sam_search_opportunities

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

Annotations already declare readOnlyHint and openWorldHint. Description adds value by noting keyless access, 50-result limit, active notices, and listed fields, which are behavioral traits not in 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 front-load purpose and key constraints (keyless, 50 results, up to date). No redundant or irrelevant words.

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?

Tool has 7 parameters and no output schema. Description covers essential return info (fields, limit, active status) and filtering hints. Lacks mention of pagination (offset) but schema covers it. Adequate for basic use.

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 86% (6/7 params have descriptions). The description mentions narrowing by NAICS/agency/set-aside/state, aligning with parameters, but adds little beyond schema details. Baseline 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?

The description clearly states it searches SAM.gov federal contracting opportunities, specifies keyless HAL, return fields (title, agency, NAICS, noticeId), and limits to 50 active notices. This is a specific verb+resource with clear scope, distinguishing it from sibling tools like sam_get_opportunity or sam_search_shaping.

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 use for discovery and narrowing by NAICS/agency/set-aside/state. While it doesn't explicitly say when not to use, the guidance is clear and contextually sufficient given sibling variety.

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