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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuinely new behavior beyond that: recurring series are expanded into individual occurrences, and the query window is capped at one year unless pagination is used. It stops short of describing pagination mechanics or result ordering, which keeps it out of the top score.

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?

Three short sentences, front-loaded with the core purpose and scope before the usage hint and the API mapping. Nothing is padded, though the trailing 'OfficeRnD: GET /bookings/occurrences' endpoint line is redundant for an agent choosing a tool.

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 an 11-parameter read-only list tool with no output schema, the description covers purpose, expansion semantics, use case and the window cap. It does not mention pagination response fields or result ordering, but the cursor parameters in the schema and the readOnlyHint annotation fill most of the remaining gaps.

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% across all 11 parameters, so the schema already carries the burden of explaining from/to, limit, cursors, filters and their formats. The description adds only the aggregate window-length rule, not per-parameter meaning, so the baseline 3 is appropriate.

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?

The description states a precise verb and resource ('List every individual booking occurrence') and immediately clarifies scope: one-off bookings plus each expanded instance of recurring series. That expansion semantics is exactly what separates it from a plain bookings listing, so an agent can distinguish it from siblings like officernd_list_bookings without opening a 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?

It gives a clear use context ('The right tool for calendars, room availability and utilisation') plus an operational rule ('Without pagination the window may be at most 1 year'). It does not, however, explicitly contrast itself with officernd_list_bookings or officernd_get_booking, so the routing guidance stops short of the top band.

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