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

Annotations already declare readOnlyHint=true and destructiveHint=false. Description adds useful context: non-binding, pricing logic (date-based vs tier), and return of discountPreview only when code is given. No contradiction.

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?

Well-structured in logical order: purpose, required/exclusive parameters, optional date/tier, partnerCode, return fields. Slightly long but every sentence adds value.

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?

Covers all 7 parameters, explains return fields despite no output schema, and clarifies behavioral subtleties (e.g., date-based vs tier-based pricing). Complete for a read-only query tool with 2 required params.

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%, but description fully compensates by explaining each parameter's purpose, format, and mutual exclusivity (captainSlug vs boatId, date vs pricingTierId). Adds meaning beyond schema types.

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?

Clear verb ('get') and resource ('non-binding price quote') with specific scope ('charter or rental'). Distinguishes from siblings like create_booking (creation) and check_availability (availability checks).

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 states parameter constraints: exactly one of captainSlug or boatId, plus durationId and partySize. Provides clear guidance on when to use date vs pricingTierId, and optional partnerCode. No confusion with alternatives.

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