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

Annotations already declare readOnlyHint=true, and the description adds real value beyond them by enumerating the returned fields and naming the REST endpoint. With no output schema, this return-content disclosure is the only place an agent learns what it gets back. It stops short of error behavior (e.g. an invalid booking code) or field formats.

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 compact sentences, front-loaded with the core action and payload before the endpoint reference. Every clause earns its place; no padding.

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 single-record read-only GET with a fully documented required parameter, the definition covers purpose, target, and return fields adequately. The only missing piece is failure behavior for an unknown booking code, a minor gap for a read tool whose annotations carry the safety profile.

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% and the single booking_id parameter is fully documented in the schema, including the CFPP-290317 example. The description adds only the URL template ({booking_id}), which is redundant with the schema. Baseline 3 applies.

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 (fetch) and resource (one booking) and enumerates the exact payload it returns — status, dates, customer, form fields, line items, totals — plus the underlying endpoint. An agent can distinguish this from checkfront_list_bookings purely from the text.

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?

The phrase 'one booking' implies the single-record counterpart to checkfront_list_bookings, but the description never states when to use this tool versus that sibling, nor any prerequisite such as needing a prior list/search to obtain the booking code. Usage is implied rather than spelled out.

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