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

The annotations already mark it read-only, and the description adds meaningful behavior: nothing is booked or held, the result includes a full fee and tax breakdown plus a payment schedule, and the possible error codes are enumerated. These details go well beyond the annotation hints.

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?

The pricing purpose is front-loaded, followed by output components, payment schedule, error codes, and the read-only clarification. Despite being dense, every element is relevant to understanding or safely invoking an exact quote.

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?

There is no output schema, but the description enumerates the returned price components, taxes, total, and payment schedule. Combined with the listed error codes and the read-only guarantee, it gives an agent enough to call and interpret the tool 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 input schema already explains each parameter, including the property enum, date formats, dog fee, discount code, and guest capacity. The description reinforces a few implications such as dog fee and discount, but adds little parameter-level meaning 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?

The description gives a specific verb and resource: returns an exact all-in price for one home over a date range, using the same pricing engine as the booking form. It is clearly a pricing tool rather than a booking tool, but it does not explicitly differentiate itself from the sibling tools check_availability and request_booking.

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?

It gives clear context for use: an exact quote for a specific home and date range, with no booking or holding. It also lists error cases that indicate when the quote cannot be produced. However, it never explicitly says when to call this instead of check_availability or request_booking.

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