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

With no annotations, the description carries the full burden and provides useful behavioral context: data source (SAM.gov), daily update frequency, Public Domain license, and the specific fields returned. It does not mention rate limits or pagination, but for a read-only search tool the disclosure is reasonably complete.

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?

Three sentences, no filler. The core action and resource are front-loaded, followed by return fields, data currency, licensing, and the authentication prerequisite. Every sentence contributes value.

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 4-parameter tool with no output schema, the description covers the essential invocation requirements: what it searches, what it returns, data source and freshness, auth requirement, and registration path. It could be stronger by noting when to use get_opportunity_detail for full details, but the current information is sufficient for correct selection and 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 100%, with each parameter already having descriptive documentation. The description adds no additional parameter-level meaning beyond what the schema provides, so the baseline of 3 applies.

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?

Description states a specific verb ('Search') and resource ('U.S. federal government contract opportunities from SAM.gov'), and enumerates the return fields (title, department, deadline, source URL). This clearly distinguishes it from siblings like get_opportunity_detail, which focuses on a single opportunity's details.

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 provides a clear prerequisite ('Requires an api_key — call register_agent first'), but does not explicitly explain when to choose search_opportunities over get_opportunity_detail or get_api_info. The usage context is implied rather than stated.

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