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

Annotations already declare readOnlyHint=true, and the embedded 'GET /holiday_allowances/{year}' reinforces that this is a non-mutating read. The description usefully details what each row contains, but says nothing about pagination limits or throttling behavior beyond what the schema already spells out.

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 sentences: returned fields first, endpoint second. Every clause carries information and nothing is padded.

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?

With no output schema, the description does the work by naming the returned attributes, which is enough for an agent to know what it gets back. The remaining gap is pagination semantics on the return side, which the schema documents for input only.

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 the year/limit/offset semantics are fully documented in the schema. The description only restates that the data is scoped to a leave year, adding no new parameter meaning. 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?

Specific verb (list) plus a clearly distinct resource (holiday allowances per employee per leave year), and it enumerates the returned fields (default/custom allowance, unit, carried over). No sibling tool covers holiday allowances, so the agent can disambiguate immediately.

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 states what the tool returns but gives no guidance on when to choose it over near-neighbours such as list_leave_types or list_leave, nor any prerequisite context. Usage has to be inferred purely from the resource name.

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