search_cars

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

The description states 'Real-time' and 'Results in ~1 second', providing performance expectations. It lists returned data fields, implying read-only operation. No annotations exist, so the description adequately covers behavioral traits.

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 concise sentences with no unnecessary words. The first sentence provides core functionality and details, the second clarifies scope. 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?

The description covers core functionality and return values, but it emphasizes airport IATA codes while the schema also allows city names, causing slight ambiguity. For a tool with 10 parameters and no output schema, it's largely complete but not fully precise.

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 have schema descriptions (100% coverage), so baseline is 3. The description adds limited parameter information beyond the schema, such as mentioning airport IATA codes but the schema already includes that.

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 verb 'Search', the resource 'car rental availability and prices', and the platform 'booking.com via AgentWeb'. It lists returned fields and differentiates from sibling tools like search_flights and search_hotels.

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 specifies that it works with any airport IATA code and gives examples of suppliers. It implies usage for car rental searches, but does not explicitly exclude when not to use or mention alternatives.

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