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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds a real operational constraint (max 1-year window unless paginated) that an agent cannot derive from the schema. It stops short of describing pagination mechanics or return shape, but the added constraint is substantive.

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 compact sentences, front-loaded with the purpose, then usage, then the operational constraint and endpoint. No filler or repetition.

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 read-only, 11-parameter list tool with no output schema and full schema coverage, the description covers purpose, scope, sibling distinction and the key window constraint. Return shape and pagination loop details are absent, but the essentials for correct invocation are present.

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 documents from/to, cursors, filters and limits thoroughly. The description only implicitly touches parameters through the 1-year/pagination remark, adding little beyond the schema. Baseline 3 applies.

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 every individual booking occurrence') and then disambiguates the resource itself: one-off bookings plus each expanded instance of recurring series. This clearly separates it from the sibling officernd_list_bookings, which an agent would otherwise confuse it with.

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?

Gives concrete usage context ('the right tool for calendars, room availability and utilisation') and implies a pagination condition via 'without pagination the window may be at most 1 year'. However, it never explicitly names officernd_list_bookings as the alternative or states when that tool is preferred, so routing is still partly inferential.

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