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

Annotations establish readOnlyHint=false (a mutation) and destructiveHint=false; the description adds substantial context beyond that, including the waiver short-circuit, the returned checkoutUrl and saleId, the inability to pay on the member's behalf, and the required NOMADSTAYS_MCP_AGENT_TOKEN. It does not contradict openWorldHint=false since the checkout URL is hosted on nomadstays.com itself.

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?

Four dense sentences with the primary action front-loaded, then waiver branch, then payment mechanics, then follow-up. No filler; every sentence carries operational weight.

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 describing the possible returns (waived status, checkoutUrl, saleId) and the auth requirement. It is nearly complete for a purchase-initiation tool, though explicit error/failure behavior is unstated.

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 both productId and applicationId are already well documented in the schema. The description adds no syntax or format detail beyond what the schema provides, 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?

'Start a purchase of a Nomad Stays product on the caller's own behalf' gives a specific verb, resource, and scope. It is clearly distinguished from the sibling getPurchaseStatus, which it explicitly names as the follow-up polling tool.

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?

States both branches of behavior: waiver-qualifying callers resolve immediately with no payment, others get a checkoutUrl. It gives explicit when-to-use routing ('hand this URL to the member... poll getPurchaseStatus... afterwards') and an exclusion ('you cannot complete payment on their behalf').

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