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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely useful behavioral context that annotations cannot convey: hourly sync cadence and a posted-to-radar latency of ≤60 minutes, which tells the agent how fresh results are. It stops short of describing pagination or result limits.

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, front-loaded with purpose and filter capabilities, with the freshness caveat last where it belongs. The parenthetical field list is somewhat dense but each item earns its place by defining the return shape in the absence of an output schema.

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 read-only search tool with no output schema, the description compensates by enumerating returned fields (title, agency, type, NAICS, set-aside, deadline, postedAt, SAM.gov link) and disclosing data freshness. Nothing critical is missing, though sibling routing is absent.

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 100%, so the schema already documents days, naics, keyword, and setAside with examples. The description restates the same filter set (NAICS, keyword, set-aside, posting window) without adding format or syntax detail beyond the schema, so the baseline 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?

The description opens with a specific verb and resource ('Explore and answer questions about federal contract opportunities') and enumerates the filter dimensions, so an agent immediately knows what this does. It does not differentiate itself from the siblings gov.digest or gov.near_expiry, which is the only thing keeping it from a 5.

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?

It gives clear usage contexts ('research a specific market, match a capability, or compare opportunities'), which is more than implied guidance. However, it never states when NOT to use this tool or names gov.digest / gov.near_expiry as alternatives for adjacent needs.

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