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

It discloses the key side effect—creating a booking—and the important output behavior: returning a Stripe Checkout link for the charterer to complete payment. It also explains the partnerCode behavior, adding value beyond the sparse boolean annotations.

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?

Two focused sentences with no filler. The primary action and output are front-loaded, and the optional partner code is clearly separated.

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?

The tool has 13 parameters, 11 required, no output schema, and no parameter descriptions. The description covers the high-level flow and one optional parameter, leaving critical details about required identifiers, payment-completion semantics, and prerequisites unspecified.

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?

With 0% schema description coverage, the description should clarify required identifiers like captainSlug, harborId, durationId, and pricingTierId, but it only explains the optional partnerCode. Most of the 13 parameters receive no semantic guidance beyond their names.

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 uses a specific verb ('Book'), names the resource ('a charter with a captain'), and states the concrete output (a Stripe Checkout link). This clearly distinguishes it from siblings like create_boat_rental and get_quote.

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 gives clear context: use this when creating a captain-led charter booking and obtaining a payment link. It does not name alternatives or list exclusions, but the intended use case is unmistakable, including the optional referrer-credit scenario.

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