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

Beyond the readOnly/openWorld annotations, it discloses genuinely useful behavior: results are links to GovDeals, Public Surplus, Municibid and Skoolie Livin' rather than mirrored listings, and the call is free with no account or auth. It does not mention result cap behavior across the multiple sources or how partial failures from one source are handled, but the key caveat an agent needs is present.

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 core purpose and the free/no-account note are front-loaded, and every clause about the three result types (dealer listings, federal surplus lots, aggregator searches) carries information. The middle sentence is a long run-on enumerating sources, which slightly hurts scannability but nothing is redundant.

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?

With no output schema, the description does the job of explaining what comes back: dealer listings, live federal auction lots, pre-filtered external searches, and category links, plus the caveat that auction/classified items are links. Missing only fallback behavior when no parameters are supplied and how the per-source limit is applied across sources.

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 pattern, ranges, defaults and examples for zip, state, radius_miles, max_price_usd and limit are already documented. The description only echoes that results are 'filtered by distance and price,' adding no semantics the schema does not already carry; 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 and resource ('Find a bus to convert into a skoolie') and even parenthetically defines the term, so the intent is unmistakable. It does not, however, distinguish itself from the sibling search_buses or get_used_bus_prices, leaving the agent to infer the boundary between a skoolie-specific finder and a general bus search.

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?

Usage is only implied: the description makes clear it is for buyers seeking a convertible bus within a distance/price budget, and notes 'Free, no account.' There is no explicit when-to-use versus search_buses or when a general listing tool would be preferable, and no guidance on required-vs-optional inputs since all five parameters are optional.

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