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

In the absence of annotations, the description provides critical behavioral context that a machine agent needs: 'Data is live from the booking engine — never cached or invented.' It also clarifies that prices include insurance and VAT, setting expectations about the returned values beyond just the numeric total.

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 dense and highly informational, front-loading the critical functional aspects (live data, availability, pricing). While slightly verbose, every sentence conveys essential, non-redundant value for the agent.

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 is exceptionally complete for a real-time search tool. It covers the geographic scope, the data integrity (live), the content of the results (cars, prices, booking URLs), and the financial inclusion (VAT/Insurance), giving the agent everything it needs to confidently invoke the tool.

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?

The description adds specific geographical and operational meaning that the schema misses, such as specifying 'Cyprus local time' and detailing that EUR and TRY are always included even if another currency is requested. This clarifies the boundaries of the `currency` and timestamp parameters.

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 is for North Cyprus car rental availability and explicitly mentions it returns actual available cars with specific financial data (prices, tax inclusion, booking link). While it doesn't name every sibling it replaces, its function is clearly defined for a live search operation.

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 implies usage by highlighting its 'live' nature, which suggests a difference from potentially static price lists or general availability lookups provided by siblings like get_booking_link or list_prices. It defines the core function of checking availability for a window.

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