govcon_search_contract_awards

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

Declares read-only, no side effects, idempotent, 4-hour cache, and verified data source. No annotations provided, so description fully covers behavioral traits.

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?

Single well-structured paragraph, front-loaded with purpose. Every sentence adds value, but slightly verbose in listing alternatives and fallback. Still concise enough.

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?

Covers purpose, parameters, usage, alternatives, source, caching, and error handling. Output schema exists but description also mentions return fields. Very complete.

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 has 0% description coverage, but description explains each parameter with defaults and examples (e.g., keyword required, agency optional, date_from format). Adds significant meaning beyond bare schema.

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 the tool searches government contract awards by keyword, agency, and date range. Distinguishes from siblings by naming specific alternative tools.

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 when-to-use (exploring competitive landscape) and when-not-to-use (vendor history, open solicitations) with named alternatives. Also includes fallback via report_feedback.

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