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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it does so well: it states this tool 'only reads the current state,' cannot lock in or create anything, requires poll_key to release the Meet link, and notes that booking confirmation already happens automatically. This is unusually clear for a read-only tool.

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 bit dense but every sentence earns its place: purpose, side-effect clarification, usage trigger, and parameter dependency. It is reasonably sized for the information it must convey, though 'Call it when the customer asks' is slightly vague.

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?

For a 2-parameter read tool with no output schema, this is complete: it states what is returned (status and Meet link), when to call it, what it does not do, and the required upstream dependency. An agent has enough context to invoke it correctly without further clarification.

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. The description adds meaningful value by explaining that a ref alone will not release the Meet link and that poll_key specifically comes from create_booking_draft and is required for the link, which is beyond what the schema states.

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 opens with a specific verb and resource: 'Retrieve a booking's status and Meet link.' It also draws an explicit contrast with create_booking_draft by stating it 'does NOT lock in or create anything,' which cleanly separates this read tool from its siblings.

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 ('Call it when the customer asks') and clarifies the dependency on create_booking_draft's poll_key. It doesn't explicitly address check_availability or list_services, but the purpose and sibling names make those exclusions obvious.

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