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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description reinforces those but adds genuinely new behavioral context: a '4-hour cache' and a 'Verified source: SAM.gov + USASpending.gov,' plus the explicit feedback loop via report_feedback. These details go beyond the structured annotations and help an agent understand caching, provenance, and what to do on failure. No contradiction exists.

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?

The description is relatively long but well-organized. It front-loads the core purpose, then covers safety, parameters, usage, and feedback in a logical order. Every sentence serves a purpose, including the encoding hint and the feedback fallback. It is not bloated; the length is justified by the added context. A minor deduction for not being more terse, but the structure is clean.

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 tool's moderate complexity (3 params, output schema present, annotations present), the description is comprehensive. It covers purpose, usage, behavioral traits (cache, source), parameter details, output fields, and a feedback mechanism. Nothing an agent needs to call it correctly is missing. The output schema likely details the return shape, so the description's mention of specific fields is a bonus.

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 all three parameters. The description adds value with a specific encoding rule for the keyword parameter: 'Encode special characters — + becomes %2B.' It also lists the return fields, which, while not parameter semantics, give the agent an idea of what the output contains. This goes beyond the baseline of 3 for full schema coverage, earning a 4.

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: 'Fetch currently open government contract solicitations matching a keyword.' It clearly distinguishes itself from the sibling govcon_search_contract_awards by stating it is for open solicitations versus historical awards, and later explicitly names that alternative. This gives an agent a precise mental model of what the tool does and how it differs.

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 gives explicit usage instructions: 'Use this when looking for active bid opportunities. Use govcon_search_contract_awards instead when you need historical awards not open solicitations.' This clearly states when to use this tool and when to use a specific alternative, leaving no ambiguity. It also includes a fallback instruction to report feedback if the tool doesn't meet the need.

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