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

With no annotations, the description carries the full behavioral burden. It does add a genuinely useful non-obvious trait — results are relevance-ranked and title matches outrank description mentions — which is not derivable from the schema. However, it is silent on result volume, pagination, whether the search is exhaustive, and any auth/rate-limit behavior.

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, both load-bearing, with the scoping content front-loaded before the ranking note. Nothing is redundant or padded.

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 4-parameter search with no annotations and no output schema, the description covers purpose and ranking but omits result-set characteristics (pagination, count limits) and any note that the ranking rule is the only ordering available. Adequate but with clear gaps for an agent deciding how to page or how broadly to query.

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%, so the four parameters are already fully documented, establishing a baseline of 3. The description restates the searchable dimensions (keyword/state/buyer level) and clarifies the open-vs-past distinction behind 'open_only', but adds no syntax or format detail 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?

States a specific verb ('Search') and resource ('government bid opportunities') and enumerates the three filtering axes (keyword, state, buyer level). The resource is distinct from every sibling (forecasts, awards, protests, recompete radar), so no confusion is possible without opening a schema.

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 never says when to reach for this tool versus siblings, nor does it state prerequisites or exclusions. The only usage signal is the parenthetical '(open and past)', which is folded into the purpose statement rather than presented as guidance.

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