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

The description adds significant context beyond the annotations: it is read-only and does not accept personal data, and it reveals that the guest makes the request, not the tool. This clarifies the tool's role and output structure.

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?

The description is a single, dense sentence that front-loads the main action and then lists the details efficiently. No unnecessary words.

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?

Given the simple read-only nature of the tool and the presence of robust annotations, the description fully covers what the tool returns (link, email subject, phone number) and its limitations. No output schema is needed for this simple use case.

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?

The description explains that the parameters (travel dates and number of people) are used to prefill the link, which adds meaning beyond the schema's basic date format descriptions. It also compensates for the undocumented 'erwachsene' parameter, whose purpose is clarified as part of the person count.

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 clearly states the tool's purpose: it delivers the two ways to make a booking request (pre-filled form link and email/phone). It also differentiates from sibling tools by specifying this is about initiating a request, not calculating prices or checking availability.

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 implies when to use it (when a guest needs to make an inquiry) and provides a clear exclusion: 'diese Schnittstelle nimmt keine persönlichen Daten entgegen' (does not accept personal data). It does not explicitly name alternative tools, but the context is clear enough.

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