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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint=false). The description adds real value beyond them: it re-checks live host calendars, expires after 10 minutes, returns house rules and a refund schedule, and does not hold inventory. It does not state auth or rate-limit behavior, so 4 rather than 5.

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?

Four dense sentences, each earning its place, with the core purpose and validity constraint front-loaded. No filler or repetition of the title.

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 and no annotation-level return info, the description usefully declares what comes back (itemized price, house rules, refund schedule). Combined with the no-reservation and expiry notes, an agent has enough to call it correctly, though parameter-level detail is still thin.

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 description coverage is 0% for 7 parameters, so the description must carry the load. 'Exact dates and party' only loosely gestures at check_in/check_out and the guest-count fields, and says nothing about pets, infants, children, or property_id formatting. Most parameters remain undocumented anywhere.

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+resource with scope: an itemized, binding price for exact dates and party. Clearly differentiated from check_availability (availability only) and request_booking (which reserves), so an agent can route correctly.

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?

Explicitly says 'Does not reserve the dates', which implies the sibling to use when a reservation is wanted, and the 10-minute validity window implies the quote must be acted on promptly. No named alternative is given, so it stops short of a 5.

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