hemmabo_booking_quote

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

No annotations are provided, but the description covers key behavioral aspects: returns specific pricing fields (publicTotal, federationTotal, etc.), notes prices are integers in local currency, and warns of potential invalidity. Could mention idempotency but sufficiently transparent.

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?

Description is concise (3 sentences) with front-loaded purpose, followed by usage guidance and return details. No fluff.

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?

Despite lacking output schema, description fully explains return values and behavior. Given moderate complexity and rich context, the description is complete enough for an AI agent to select and invoke correctly.

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 descriptions already cover all 4 parameters (100% coverage). The tool description adds value by explaining pricing logic (staircase pricing by guest count) and listing return fields, supplementing the schema without redundancy.

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 'Get a detailed pricing quote' with specific parameters (property, dates, guests). It distinguishes itself from sibling tools by noting it should be used after checking availability, contrasting with search/availability tools.

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?

Explicit guidance: 'Use this tool after confirming availability... Do NOT use before checking availability—the quote may be invalid if dates are unavailable.' This provides clear when-to-use and when-not-to-use instructions.

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