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

Annotations only declare it isn't read-only but isn't destructive, which is thin for a sharing tool; the description adds real behavioral disclosure: invitee email, phone and notes are never exposed, the meeting link is gated behind `includeLink`, and re-invocation is idempotent on `url`. It doesn't cover authorization requirements or what the returned page/URL looks like, keeping it below a 5.

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?

Two front-loaded sentences with no filler: the first establishes what the page shows, the second covers privacy, the link flag, re-call semantics and the off-switch. Every clause carries distinct information.

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, the description usefully signals that the result is a `url`, and it covers privacy and link exposure, which matter most for a sharing action. It omits error/precondition behavior (invalid or canceled booking) and permission requirements, so it is strong but not fully complete.

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 the baseline is 3, but the description adds meaning the schema lacks: it frames style/includeLink as changeable on repeat calls and ties `includeLink` to a concrete risk (anyone with the link can join) and recurrence to `url` stability. `id`/`token` semantics are still left entirely to 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?

The description uses a specific verb and resource ('Turns a confirmed booking into an invitation page') and constrains scope ('anyone with its `url` can open'). It also names the sibling that reverses it (stop_sharing_booking_as_invitee), so an agent can separate it from get_shared_booking and the other booking tools without opening a schema.

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 says clearly it applies to a confirmed booking and tells the agent that re-calling is a legitimate way to change style or link while preserving the same `url`, plus it names stop_sharing_booking_as_invitee as the ending alternative. It doesn't state prerequisites (such as whether token must be a manage token) or when to prefer get_shared_booking instead, so it falls short of full when/when-not guidance.

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