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

Annotations only declare the generic mutation profile (readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false); the description adds far more: that it creates a booking/room but sends no invitation, email or owner reminder, that reservation is atomic, that it does not authorize sending email or calendar sync, and that hostJoinUrl is private while guestUrl is the shareable link.

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?

Front-loads the core action and follows with constraints in a logical order; every sentence carries operational content. It is on the long side at eight sentences, but there is no filler or repetition.

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 helpfully names the return values (confirmed guestUrl, schedule, host timezone, optional hostJoinUrl), which an agent needs for the email-drafting follow-up. Minor gaps remain around authorization/permission requirements and the meaning of leadId/locale.

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 description coverage is 0% across 7 parameters, so the description must compensate and only partly does: it clarifies service/resource (canonical names from get_meeting_availability), startsAt ('selected service time') and requestId (UUID reused on retries). It says nothing about title, leadId, or locale, nor any format constraints, leaving three of seven parameters undocumented anywhere.

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?

States a specific verb and resource ('Prepare a guest room link'), then spells out the composite action: recheck availability, atomically reserve the service time, and auto-create a branded video room. It is clearly distinguishable from sibling write tools such as create_meeting and prepare_booking_link, and it names get_meeting_availability as the prerequisite read step.

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?

Gives explicit sequencing ('First use get_meeting_availability'), an explicit prohibition ('never bypass a stale/concurrent conflict'), an alternative path when a room already exists ('use list_meetings/get_meeting instead of creating another'), and retry semantics via requestId. Both when-to-use and when-not-to-use are covered.

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