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

Annotations already declare readOnlyHint=true, so the agent knows this is a safe read. The description reinforces the read-only nature and lists the fields returned, but adds no auth requirements, rate-limit behavior, or not-found handling, so it adds only modest context beyond structured data.

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 compact sentence front-loads the action and resource, then lists fields and the endpoint. Nothing is wasted or buried.

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 simple single-record read with full schema coverage and readOnlyHint annotation, the description supplies the lookup key, the returned field set, and the underlying endpoint. Since no output schema exists, the field enumeration is useful and no critical agent need is missing.

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 sole parameter's description ('The booking _id.') already explains the input. The description's 'by _id' phrasing is consistent but adds no syntax, format, or constraint detail beyond the schema.

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?

Specific verb 'Fetch' plus resource 'one booking' and the exact lookup key '_id'. Enumerates the returned payload (resource, member/company, times, recurrence rule, fees, extras, visitors, status) and cites the underlying GET endpoint, distinguishing it clearly from the list_* booking siblings.

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?

Makes the trigger condition clear: use when you have a single booking _id and need that record. However, it does not name alternatives such as officernd_list_bookings or officernd_list_booking_occurrences or state when not to use it, so it stops short of full when/when-not guidance.

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