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

Goes well beyond the annotations by disclosing server-side price/availability re-validation, rejection behavior for stale quotes, the out-of-band payment model (member opens checkoutUrl in their own browser; no card details pass through), and the required NOMADSTAYS_MCP_AGENT_TOKEN 'bookings' scope. This is exactly the behavioral context annotations readOnlyHint/destructiveHint cannot convey.

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 purpose in the first clause, then layers prerequisite, failure handling, and the payment hand-off rule. Every sentence carries distinct, actionable 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?

For a tool with no output schema, the description still explains the return (hosted checkoutUrl) and the full lifecycle: quote → re-validate → create → hand off to member. Auth scope, error path, and payment constraints are all covered, leaving no operational gap.

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 documents all five parameters including defaults for contactName/contactEmail. The description reinforces that quoteId is the driving input but adds no new format, constraint, or example meaning beyond the schema, warranting the baseline 3.

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 ('Create a real booking from a quoteId') and the return value ('hosted checkoutUrl'), and names the sibling quoteStayBooking as the source of the required input. An agent can distinguish this from quoteStayBooking and the many create* application siblings without opening a 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 defines the prerequisite (a quoteId from quoteStayBooking), the failure path for stale/expired quotes ('call quoteStayBooking again'), and the mandatory post-call action (send the checkoutUrl to the member for them to pay). The when-to-use flow is fully specified with no ambiguity.

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