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

Annotations only cover readOnly/idempotent/openWorld/destructive, but the description adds rich behavior: availability rule ('only properties with a room or unit free for every night'), sort order ('cheapest first, exact town matches first'), pagination, full result field inventory, deposit handling, the partner fallback path, commission disclosure, and the fact that only location text is sent to Trip.com.

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 purpose is front-loaded correctly, but the body is a dense wall of clauses covering deposits, partner terms, and data-sharing that could be tightened. Sentences do carry real information, yet the sheer density hurts scannability for an 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?

For a 15-parameter tool with no output schema, the description compensates well by enumerating returned fields (nightly price, total_price, cancellation policy, room counts, deposits) and explaining the partner_results branch with pricing, stars and currency applied. Nothing essential for correct invocation seems missing.

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 73%, so most parameters are documented in the schema itself (stars, currency, price filters, property_type, whole_home). The description reinforces currency/price semantics and sorting behavior tied to location matching, but adds little that the schema does not already convey, and says nothing about min_beds/min_bedrooms/min_bathrooms.

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?

Opens with a specific verb and resource ('Find independent stays bookable direct on Bookd'), enumerates the property types covered, and scopes it by location and dates. An agent can immediately distinguish this search tool from get_property, check_availability, or request_booking.

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?

Clearly frames the tool as read-only ('nothing is booked or held') and gives an explicit when-not rule for a sibling ('Never call request_booking for them' regarding partner hotels). It lacks explicit guidance on when to prefer this over check_availability or get_property, so it falls short of a full 5.

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