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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses pricing ($0.002 USDC per successful call via x402), that failed calls are not charged, that only public teaser fields are returned, and that full bid documents require a separate BidNet Direct vendor account. These are meaningful operational details an agent needs before invoking the tool.

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 a compact paragraph that front-loads the core scope and source, then layers in pagination, field limits, account requirements, and pricing. Every sentence adds operational value with no filler.

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?

Given that an output schema exists and the input schema is fully documented, the description supplies the remaining context an agent needs: source, geography, result ordering, page size, teaser-field limitation, account requirement for full documents, and cost model. Nothing material is omitted for correct invocation.

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 the baseline is 3. The description adds meaning beyond the schema by specifying that results are 'newest first' and that keyword search is the mechanism, while the schema already defines page range and empty-query behavior.

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 states a specific resource—open US/Canadian government bid solicitations from BidNet Direct's free public search—and names the covered levels (state, local, federal). It distinguishes itself by source from tools like gov_canadabuys_tenders or gov_ted_eu_procurement, though it does not name any sibling explicitly.

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 gives useful context: keyword search, newest-first ordering, 25 per page, and the fact that only public teaser fields are available. However, it does not explicitly say when to use this tool versus the many other tender tools in the sibling list, nor does it name alternatives.

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