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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is carried by structured data. The description adds useful surface detail (returned fields, approved-only scope, the GET /absences endpoint), but says nothing about pagination or the next_page contract implied by the page parameter. Adequate but not rich.

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: what is returned, how to filter, then the endpoint. Front-loaded with the value proposition and zero filler. Nothing to trim.

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 no-required-param read tool with a rich schema and annotations covering safety, the description is close to sufficient: scope, returned fields, and filters are all present. It stops short of the routing guidance (vs. leave_requests/sicknesses) and pagination behaviour that would make it fully self-contained.

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 each of the nine parameters is already documented in the schema. The description restates the same filter set (employee, department, type, reason, dates, cancelled) without adding format or interaction detail. Baseline 3 applies when the schema does the heavy lifting.

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 approved absences') and enumerates the returned fields (employee, dates, half days, days deducted, cancelled flag). The 'approved absences (holiday and other leave)' scoping distinguishes it from the sibling breathehr_list_leave_requests, which covers the request workflow rather than recorded absences.

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 lists filter dimensions but never says when to reach for this tool versus breathehr_list_leave_requests or breathehr_list_sicknesses. No exclusions or prerequisites are stated, leaving the agent to infer the boundary itself.

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