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

readOnlyHint=true already declares the safety profile, so the bar is lower, but the description adds no behavioral context beyond the raw endpoint path — no pagination behavior, no default page size, no statement about whether results are ordered or complete. The one genuinely useful clarification (offers = quotes sent to clients) is definitional rather than behavioral.

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 compact fragments with the purpose and the disambiguating gloss front-loaded, followed by the endpoint. No filler. It is arguably a touch too terse, but nothing is wasted.

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 simple read-only list tool with fully documented parameters and an explicit readOnlyHint, the description covers the essentials. However, with no output schema, it gives no hint about what fields an offer record contains, which an agent needs to decide whether this is the right source for quote data.

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%: page, per_page, and search_string are all documented in the schema, including the default and the 200 cap. The description adds nothing about parameter semantics, so the baseline 3 applies.

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 booking offers") and adds a clarifying gloss — "quotes sent to clients" — that disambiguates it from the sibling limoexpress_list_bookings. The REST endpoint is included as supplementary evidence. It stops short of naming a sibling to contrast with explicitly, but an agent can tell what this returns.

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 by the parenthetical definition of an offer as a quote; there is no explicit when-to-use or when-not-to-use guidance versus limoexpress_list_bookings or limoexpress_list_booking_statuses. No prerequisites, no note on whether offers are filterable by client or status. Adequate but clearly incomplete for an agent choosing among 21 siblings.

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