search_vehicles

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

No annotations are provided, so the description carries the burden. It implies a read-only search operation but doesn't explicitly state side effects, authorization needs, or data behavior beyond the ad nature. The 'search' verb and classified-ads wording provide implicit transparency, but explicit statements would be stronger.

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 single, information-dense sentence that conveys the tool's purpose, subject, key filters, and the critical distinction from product listings. No unnecessary words or repetition, and it's well-structured.

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 needn't detail return values. It covers what the tool does, the type of content, and the important non-product nature. It doesn't discuss pagination or result format, but that's not required given the schema already has limit/page parameters. The main context is complete.

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?

All parameters are described in the schema (100% coverage), so the baseline is 3. The description adds domain context (vehicles, classified ads) and highlights specific relevant filters, but it doesn't elaborate on each parameter beyond the schema descriptions, which are brief but adequate.

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 the tool searches classified vehicle ads for cars and motorbikes on Toco, with an explicit note that these are contact-the-seller ads, not add-to-cart products. This both states the primary purpose and distinguishes it from other search tools like search_products.

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?

It explicitly mentions the supported filters (production year, mileage, transmission) and clarifies the ad type, making it obvious when to use this tool instead of search_products or search_properties. It doesn't reference sibling tools by name but the domain and constraints are sufficient.

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