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

No annotations are provided, so the description carries the full disclosure burden, and it discloses almost nothing behavioral. It implies a read-only search and hints the data is "historical" (i.e., past awards, not current pricing), but says nothing about pagination, result limits, data coverage, or what fields come back.

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?

Two short sentences with zero filler, and the core purpose (search federal award data) is front-loaded before the price-intelligence rationale. Every sentence earns its place.

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 four-parameter, all-optional search tool with no output schema and no annotations, the description is minimally adequate: it says what is searched and roughly what is returned (prices paid, winners). It omits result shape, data recency/coverage, and any routing guidance relative to its three siblings.

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 all four parameters (limit, naics, agency, keyword) are already documented in the schema. The description adds no filtering syntax, NAICS guidance, or keyword-matching semantics beyond what the schema states, 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?

States a specific verb (search) and a specific resource (historical US federal contract award data), plus the intent (price intelligence). However, it never distinguishes itself from the sibling search_contracts, which by name appears to cover very similar ground, leaving the agent to guess which to call.

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?

"For price intelligence" and "find out what similar contracts paid" imply the scenario in which this tool is appropriate, so usage is inferable. But there is no explicit when-to-use/when-not statement and no mention of the sibling alternatives (search_contracts, search_grants, search_spending) that an agent must choose between.

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