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

Goes well beyond the annotations: it discloses that the desk replies out-of-band to the person's own email or phone, that this tool's own answer only confirms receipt and the destination, and that nothing is booked or paid until the person confirms with the desk. Those are exactly the side-effect facts an agent needs and none are derivable from readOnlyHint=false / destructiveHint=false alone.

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?

Front-loaded with the purpose, then inputs, then outcome, then the safety constraint — a sensible ordering with no filler. The sentences are long and comma-heavy, which costs a little scannability, but 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 an output schema present and full schema coverage, the description only needs to supply the semantics the structured fields cannot: the out-of-band delivery, the non-booking nature, and the consent requirement. It supplies all three, leaving no material gap for a 9-parameter tool.

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%, so the schema already explains every parameter including the email/phone/session fallback and the 20-item cap. The description restates the same groupings ('the page links... the days and the party... anything the person wants the desk to know') without adding format or constraint detail, 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 ('Ask this site's desk for a formal quote on one or more yachts') and makes clear it is a downstream step from the search tools, not a search itself. An agent can distinguish it from search_yachts, best_deals, get_yacht and price_range without opening any schema.

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 to pass the page links that 'a search, best_deals or get returned', which establishes the correct call ordering relative to siblings, and adds the consent rule 'Ask the person before calling it.' It stops short of naming an explicit when-not or a named alternative for a different outcome, but the usage context is unambiguous.

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