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

Annotations already declare readOnlyHint=true, so the safety profile is covered by structured data. The description adds genuine behavioral context beyond that: the de-duplicated result grain (recurring series collapse to their first instance), which materially changes how an agent should interpret the response. It does not discuss pagination behavior or the cursor round-trip, which are only implied by the schema.

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?

Front-loaded with the highest-value information (the result grain) and finished in three short sentences with no padding. The trailing 'OfficeRnD: GET /bookings' endpoint note is low-value for an agent but costs only a few tokens.

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?

All 12 parameters are optional and fully described in the schema, and there is no output schema, so the description only needs to disambiguate the tool and explain the result grain — which it does. It could say slightly more about pagination behavior given the two cursor parameters, but nothing essential 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 description coverage is 100%, so every one of the 12 parameters is already documented in the schema, including the ISO 8601 format and cursor semantics. The description restates the filter dimensions but adds no syntax or behavior beyond the schema, so the baseline 3 is correct.

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 ('List bookings') and immediately pins down the result grain: one entry per one-off booking and one per recurring series, first instance only. That grain definition is what separates it from officernd_list_booking_occurrences, so an agent can pick between them without opening either schema.

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?

Names the alternative tool explicitly ('For every individual occurrence in a date window use officernd_list_booking_occurrences') along with the condition that selects it. It also enumerates the filter axes (member, company, location, resource, series start window, status), so the agent knows what this tool is for.

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