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

readOnlyHint=true already covers the safety profile, so the bar is lower; the description still adds real behavioral context by disclosing that dates change the response shape and that the rated response carries a SLIP token needed for booking. No contradictions with annotations.

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 tight sentences, front-loaded with the core action and then the mode difference and the SLIP hand-off. Nothing is repeated from the schema and every clause carries information.

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 13 params, one nested object and no output schema, the description compensates well by explaining that the no-date and dated responses differ and what the dated one contains. It leaves minor gaps around filtering params (keyword, category_id, item_id) but those are fully documented in the schema.

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 100% and the schema already marks each rated parameter with '(rated)' plus formats, so the description earns only the baseline. It does add the pairing intuition (start_date plus end_date / param quantities) but no syntax or constraint detail beyond the schema.

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 and resource ('List the enabled inventory items') and enumerates the item types covered (tours, activities, rentals, rooms). It also distinguishes the two modes of the tool — plain catalogue vs RATED response — which no sibling duplicates.

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 when to omit dates (plain catalogue) vs when to pass start_date/end_date (rated response with availability, pricing, SLIP). It even names the downstream consumer, checkfront_add_to_booking_session. It does not, however, route the agent away from near-neighbours like checkfront_get_item or checkfront_get_availability_calendar.

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