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

Annotations already declare readOnlyHint=true, so safety is covered; the description goes further by disclosing the exact response envelope ({ items, count, limit, offset, next_page_url }) and the fact that `params` is merged verbatim with the typed parameters. It does not mention rate limits or auth requirements, which keeps it out of the 5 range.

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?

Three short sentences: purpose, endpoint, return shape, then param guidance. The scoping and return information is front-loaded and every clause carries distinct information with no 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?

With no output schema, the description compensates by spelling out the response envelope and pagination fields, and the passthrough guidance covers the one non-obvious parameter. An agent has everything needed to page through quotes correctly.

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 baseline is 3, and the description earns an extra point by naming concrete filter keys (property_id, guest_id) that appear nowhere in the schema, clarifying what the open-ended `params` object is actually for. It does not explain merge precedence conflicts between `params` and typed params.

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 quotes") and pins it to the underlying API endpoint GET /v2/quotes, so the agent knows this enumerates the quotes collection rather than fetching a single one like get_quote. It stops short of explicitly naming the singular sibling to differentiate scope, so it lands just under the top mark.

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?

The description tells the agent how to reach documented filters ("Use the `params` passthrough for documented filters (e.g. property_id, guest_id)"), which is real usage guidance. However, it never says when to prefer this tool over get_quote, list_bookings, or ownerrez_request, so the alternative-selection question is left to inference.

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