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

readOnlyHint=true already covers the safety profile, but the description goes further by enumerating the returned fields, which matters because there is no output schema, and by mapping to the underlying REST call (GET /bookings/{bookingId}). It does not mention not-found/error behavior, which keeps it below 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?

Two compact clauses with the purpose front-loaded, followed by the payload scope and the API mapping. Nothing is padded and no sentence is wasted.

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-parameter read tool with no output schema, the description compensates well by listing what the returned booking contains. The only gap is operational behavior on an unknown/invalid booking _id, which an agent might want before calling.

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 booking_id parameter is documented as 'The booking _id.' The description's 'by _id' only echoes the schema, adding no format, sourcing, or validation detail beyond it — the baseline 3 for full schema coverage.

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 and resource ('Fetch one booking by _id') and the word 'one' cleanly separates it from the sibling list tools (officernd_list_bookings, officernd_list_booking_occurrences) that return multiple records. It also enumerates the payload contents (resource, member/company, times, recurrence, fees, extras, visitors, status), so the agent knows exactly what it is retrieving.

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 description never states when to use this tool versus the list tools, nor any prerequisite (e.g. needing a valid booking _id from a prior list call). Usage is only inferable from the tool name and the phrase 'by _id'.

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