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

With no annotations, the description carries the full load and does so well: it discloses that the call is a no-op (holds nothing, takes no details) and describes the exact return payload — a WhatsApp link, a pre-written neutral message, and the contact page address. That is exactly the non-obvious behavior an agent needs before invoking.

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 short sentences, front-loaded with the availability caveat, then the return contents, then the user-facing action. No sentence is redundant.

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?

There is no output schema, and the description compensates by enumerating what is returned. For a parameterless, side-effect-free tool, nothing needed to call it correctly is missing.

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?

Zero parameters, so the 4 baseline applies. The description reinforces this by explicitly stating it takes no details, leaving no ambiguity about missing inputs.

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 states precisely what the tool does (returns a WhatsApp link to the agent plus a contact-page address) and explicitly negates the name's implication by saying booking is not open and nothing is held. It implicitly separates itself from the booking-lifecycle siblings (confirm_booking, cancel_booking, check_booking) by stating no details are taken, though it never names an alternative.

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?

It gives a clear trigger for acting on the result: show the link if the user wants to talk to the agent. It also warns that calling the tool by itself accomplishes nothing, which steers the agent away from treating it as a real booking. No sibling alternatives are named, so it stops short of a 5.

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