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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new context beyond that: the enumerated set of possible states, the presence of a 'reason', 'next_step', and time/meeting-type fields, and the privacy scoping note 'Never returns the guest's details' — but it omits permission/auth requirements.

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 compact sentences, front-loaded with the workflow anchor before the substantive return-value detail. The state enumeration is dense but load-bearing; little text is wasted, though the opening guide reference could be tightened.

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 carries the return contract itself — it names the possible states, the extra fields (reason, time, meeting type, next_step), and what is deliberately omitted (guest details). Combined with annotations covering safety, an agent has everything needed to call and interpret this tool.

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 100% and the single parameter carries both a format pattern and a provenance note ('the booking_id book_meeting returned'). The description adds no parameter syntax or format detail beyond the schema, so the baseline 3 for schema-led parameters is correct.

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+resource ('get the state of a booking by its ID') and enumerates the exact state space (pending_confirmation, confirmed, declined, expired, cancelled). It also positions itself in the workflow as step 6 of get_booking_guide, so it is clearly separable from siblings like book_meeting and cancel_booking.

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?

Anchoring usage to 'Step 6 of the booking guide (get_booking_guide)' tells the agent when this call belongs in the flow. It does not, however, explicitly state when NOT to use it or name an alternative for related needs (e.g. cancel_booking), 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.