govcon_fetch_vendor_contract_history

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

With no annotations, the description fully discloses: read-only, no side effects, idempotent, fuzzy matching, caching (4-hour cache), verified source, and fallback feedback mechanism. This is comprehensive.

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 well-structured with front-loaded key traits. Though slightly lengthy, every sentence adds value. Could be tightened but not a major issue.

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, behavior, source, caching, and fallback. With an output schema present, it explains return content (award value, agencies, types, recent awards) sufficiently.

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 0%, so description adds crucial meaning: vendor_name description with example, required flag, fuzzy match hint; jurisdiction enum values and default. Compensates fully.

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 it fetches 'complete federal contract award history for a specific vendor', using a specific verb and resource. It explicitly distinguishes from the sibling tool govcon_search_contract_awards by specifying when to use each.

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 (research a specific vendor) and when-not-to-use (use sibling for topic exploration). Also clarifies optional jurisdiction and default, aiding decision-making.

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