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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavior beyond that: owner-only visibility of private details like confirmation codes, the semantics of an unresolved payment_state, and the fact that refund settlement is separate from reservation confirmation.

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 read purpose is front-loaded in the first sentence, and the payment_state warning is placed before the more peripheral notes. 'Effects: None.' is largely redundant with readOnlyHint/destructiveHint but is a conventional, low-cost disclosure.

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 appropriately characterizes what is returned ('canonical reservation and payment state') and covers access control and side effects. It leaves the exact returned fields unspecified, but for a single-object read whose annotations already convey safety, an agent has enough to call it correctly.

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?

There is only one parameter and schema description coverage is 100%, with the schema itself documenting the bkg_ prefix and where the reference comes from. The description adds no parameter-level detail, so the baseline of 3 applies when the schema does the heavy lifting.

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 gives a specific verb ('Reads') and resource ('the canonical reservation and payment state of one booking'), which clearly scopes it as a single-booking lookup rather than a listing. It is clear enough to separate from anywayr_list_bookings, but it never names or contrasts with any sibling explicitly, so it lands just short of the top tier.

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 real conditional guidance: when payment_state is needs_review the agent should read the booking or contact support, and explicitly must NOT start a new booking or claim no charge was made. That is strong when/when-not guidance, though it stops short of routing the agent among named sibling tools.

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