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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the read semantics need no restatement. The description nevertheless adds genuine value by enumerating the four possible states and disclosing downstream effects: completed carries the hotel's own confirmation number and the traveler is emailed, and complete_in_progress means the advisor is actively placing the reservation. It does not cover error behavior for an invalid or expired session_id.

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?

A single front-loaded sentence with a compact state enumeration; the parentheticals earn their place by conveying approval/implicit side effects. The leading 'READ.' is redundant against readOnlyHint=true and is the one wasted token.

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 one-parameter read tool with no output schema, the description covers the key return semantics by naming every terminal and in-flight state and what 'completed' carries. What the response otherwise contains (other session fields) and how failures surface is left unstated, so it falls just short of 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 description coverage is 0%: session_id is typed string but has no schema-level definition, and the description never mentions the parameter or where to obtain it (e.g., from create_booking_session). The parameter is self-evident from its name, which limits the damage, but the description does nothing to compensate for the coverage gap.

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 states a specific resource (a booking session) and what it returns (current state), and the title reinforces the read intent. It does not distinguish itself from nearby siblings like get_booking_status or get_trip_details, which an agent could plausibly confuse with this tool.

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?

Usage is only implied: having a session_id, you call this to check where the session stands. There is no explicit guidance on when to prefer this over get_booking_status, get_trip_details, or get_booking_session's mutation siblings, and no preconditions are stated.

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