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

Annotations only declare readOnlyHint=true, so the description usefully adds the plan-level prerequisite (Basic plan) and the hard 366-day date-range constraint, neither of which appears in structured fields. It also summarises the status vocabulary returned. It stops short of describing pagination/return shape, but 100% schema coverage on limit/offset covers that.

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-loads the core action and scope, then appends the two operational facts (plan requirement, endpoint) as short sentences. The mid-sentence list of returned fields is slightly dense but every element is informative; nothing is wasted.

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 compensates by enumerating the returned fields (employee, type, dates, hours/days, status, reviewer) and by stating the plan and range limits. Coverage is solid for a 9-parameter list tool, though pagination behaviour is left entirely to the schema.

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% and every parameter is documented inline, so the schema carries the semantics. The description reinforces the date-range constraint but adds no format or syntax detail beyond what min_date/max_date already declare.

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 (List) and resource (absences), and parenthetically defines the scope of what counts as an absence: leave, sick leave, other time off. This differentiates it cleanly from shiftbase_get_absence (singular fetch) and shiftbase_list_absence_types.

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 real preconditions – the Basic plan requirement and the 366-day maximum range – which help an agent know whether the call will succeed. However, it never states when to prefer this over shiftbase_get_absence or how it relates to list_absence_types beyond the enum hint in the schema; usage is implied rather than spelled out.

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