hemmabo_booking_negotiate

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

Discloses binding nature, 15-minute lock period, and outputs (quoteId, totals, expiry). Without annotations, this is strong, though it could mention whether the quote is idempotent or if multiple quotes per property are allowed.

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?

Three focused sentences: first states purpose, second gives usage direction, third lists return values. No redundancy, information is front-loaded.

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, description fully covers return values (quoteId, totals, breakdown, expiry). Usage flow is complete: use before checkout, quote locks price for 15 minutes. No missing information for a well-defined task.

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 coverage is 100%, so baseline is 3. Description adds context: propertyId should be from search, guests determines price tier, and checkIn must be today or later. This adds meaningful value beyond the schema.

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?

Description clearly states the tool creates a binding price quote that locks price for 15 minutes, and distinguishes from sibling tools like hemmabo_booking_checkout and hemmabo_booking_quote by specifying its role as a prerequisite for guaranteed pricing.

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 instructs to use before hemmabo_booking_checkout for price certainty, warns against skipping, and explains consequences (fresh price calculation without quoteId). Provides clear when-to-use and when-not-to-use guidance.

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