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

Annotations already cover read-only, idempotent, non-destructive and open-world traits, so the bar is lower; the description still adds real value by disclosing that prices are masked RoomLast bands and that results carry public-rate comparisons and links, and by stating the exclusion of exact private prices and room options. It omits pagination behavior despite a page parameter.

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 sentences, front-loaded with purpose and scope before the filter and return-value summary. The filter enumeration partially restates the schema and could be trimmed, but no sentence is filler.

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 20-parameter search tool with an output schema, the description covers purpose, date semantics, filter scope, and result shape adequately. Minor gaps: no note on pagination limits or how masked price bands should be interpreted downstream.

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 90%, so the baseline is 3; the description adds meaningful semantics by explaining the two date modes (dateIntent 'tonight' versus the checkinDate/checkoutDate pair) and by grouping the filter families (occupancy, price, stars, guest score, property type, amenities, cancellation, sort) into a coherent mental model.

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?

Specific verb ('Finds') + resource (last-minute hotels) + geographic scope (city, neighborhood, airport, landmark) + date scope (tonight or upcoming dates). The closing sentence about what is excluded (room choices, exact private prices) implicitly distinguishes it from get_accommodation_offers and get_accommodation_details.

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?

Clear context for use: last-minute stays for tonight or specified dates, with the supported filter families enumerated. It signals the boundary against offer/detail tools by stating results exclude room choices and private prices, but never names those sibling tools explicitly, so the routing is implied rather than spelled out.

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