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

With no annotations, the description carries the full behavioral burden. It does add real value by disclosing the pricing rules (21% VAT, 500 km/day included, 3.50 CZK/km over-limit), but it never states that the call is read-only, what the response contains, or whether the quoted price is per vehicle or aggregate.

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 tight sentences with the core capability front-loaded and the pricing policy following as supporting detail. Nothing is redundant or padded.

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 should clarify what 'dostupnost' returns — a boolean, a list of available vehicles, or a price quote — especially given the optional vehicle_id. It is adequate for a simple check but leaves the return shape and the no-vehicle_id behavior ambiguous.

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% and all three parameters are documented in the schema, so the baseline is 3. The description's mention of 'zadaném období' loosely maps to from/to but adds no format or semantics beyond what the schema already provides, and it says nothing about what happens when vehicle_id is omitted.

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 verb and resource: it checks vehicle availability for a given period and computes the total rental price including 21% VAT. That is clearly distinct from create_booking, get_fleet_info, and calculate_load_compatibility, though the description never names a sibling to reinforce the distinction.

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 — 'v zadaném období' suggests this is the pre-booking availability/price check, but the description never says when to use it instead of create_booking or get_fleet_info, nor does it state any prerequisites.

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