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

Annotations only declare the generic safety profile (not read-only, non-destructive, open-world); the description adds the real behavioral detail: the awaiting_payment branch, the 60-minute card window, the payment_url/agent_payment return, the pending_host_confirmation transition, and immediate host routing otherwise. This is rich context well beyond structured fields.

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-loads the core action in the first sentence, then layers the conditional payment behavior and return/poll guidance. Dense and occasionally run-on, but nearly every clause carries operational value 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 carries the return-value burden and does so by naming the booking, status link, payment_url, and agent_payment, plus the get_booking polling path. Missing only prerequisites like auth or quote expiry for full completeness.

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 0% across 7 parameters, so the description must compensate. It clarifies the semantics of house_rules_accepted (a consent gate tied to the quote's rules) and implies quote_id comes from a quote, but says nothing about email, phone, name fields, or special_requests constraints.

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 ('Request a stay from a quote') and names the input that anchors it (quote_id). It is clearly distinguishable from siblings like get_quote, get_booking, and cancel_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?

Gives explicit conditional guidance: set house_rules_accepted only after the guest has seen and agreed to the rules, and spells out what happens depending on payment.collected_by. It routes the agent to get_booking for polling but does not name other alternative tools or preconditions such as auth.

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