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

readOnlyHint=true already tells the agent this is a safe read. Beyond that, the description adds real value by disclosing what the payload contains (form fields, line items, totals) and mapping to the underlying GET endpoint, which is useful given there is no output schema. It omits auth/permission and rate-limit context, so it is not a 5.

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?

One sentence enumerating the payload plus a short endpoint mapping — front-loaded with the verb and resource and free of padding. Every clause earns its place.

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 burden of describing return content and does so reasonably well for a single-key read tool. The only meaningful gap is the absence of any routing guidance relative to the sibling list/session tools.

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 is documented with a concrete example ('CFPP-290317'), so the description is not needed to explain it. The description adds no format or semantics beyond what the schema already carries, which is the expected baseline.

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 returned data shape (status, dates, customer, form fields, line items, totals). The 'one booking' phrasing implicitly separates it from checkfront_list_bookings, but it never names or contrasts with that sibling explicitly.

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: the agent infers this is the detail-fetch counterpart to list_bookings, and the required booking_id implies a prior lookup. There is no statement of when to prefer this over checkfront_get_booking_session or checkfront_list_bookings, and no prerequisites stated.

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