govcon_search_contract_awards

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

Discloses return fields (award amounts, recipient vendors, NAICS codes, award dates) and cache duration (4-hour cache), adding value beyond annotations which already indicate read-only, idempotent, and open-world hints.

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?

Concise yet comprehensive paragraph, front-loading the core purpose, with no redundant sentences; each sentence adds specific 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?

Covers all necessary aspects: purpose, parameters, alternatives, data source, caching, and expected return fields, making it fully self-contained for an agent.

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 good descriptions, but the description adds real-world examples and clarifies parameter usage (e.g., 'keyword: Contract scope e.g. 'cybersecurity software''), enhancing semantics beyond the 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?

The description clearly states the verb 'search' and resource 'government contract awards', and distinguishes from siblings by explicitly naming alternative tools for different use cases.

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 guidance on when to use this tool vs alternatives ('Use govcon_fetch_vendor_contract_history...', 'Use govcon_fetch_open_solicitations...') and mentions data source and cache behavior.

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