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

Adds real value beyond the readOnly/idempotent/non-destructive annotations: it names the required `bookings:read` scope and warns that human-authored text arrives in untrusted_fields and must be treated as data, not instructions. That prompt-injection guard is a meaningful behavioral disclosure not captured anywhere in structured fields. It stops short of describing not-found or permission-denied behavior.

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?

Two short sentences, front-loaded with purpose followed by the auth scope and the safety caveat. Every clause carries information an agent needs; nothing is redundant.

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 an output schema absent, the description covers purpose, auth requirement, and the shape/safety of returned human text. Only error outcomes and the distinction from the listing sibling remain unaddressed.

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%, so the description is the only place proposal_id could be explained, and it only implies that the identifier selects a request or offer. It adds no format, source, or acquisition guidance (e.g., where to get the id). With a single required parameter the gap is small but real.

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?

Uses a specific verb ("Get") and clarifies domain vocabulary by mapping the resource to "a request or offer," which is more informative than the tool name alone. It does not explicitly distinguish itself from siblings like list_booking_proposals or get_booking_overview, but the singular retrieval framing is clear.

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?

No when-to-use guidance is given: nothing says to use this after listing proposals, or when to prefer it over get_offer_defaults / preview_booking_request. The required proposal_id hints at single-item retrieval, but that inference is left entirely to the schema.

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