Time-off requests

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

Annotations already mark this as read-only, idempotent, and non-destructive. The description adds valuable behavioral context beyond that: health-related absences are reduced to type 'absent' with no notes, results are scoped to what the API key owner may see, and a per-call record limit applies. This is useful and does not contradict the annotations.

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 sentences with no filler: the first states the action and scope, the second adds a non-obvious behavioral transformation, and the third adds visibility and limit constraints. The key information is front-loaded.

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?

The description covers the core behavior, optional filters, privacy scoping, redaction, and record limits, while the schema supplies formats and defaults. Without an output schema, a little more return-shape detail could help, but the description is adequate for selecting and invoking the tool correctly.

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 coverage is 100%, so start/end formats, status enum, employeeId, and timeOffTypeId are already documented structurally. The description only paraphrases the filter dimensions rather than adding new parameter-level semantics.

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 uses a specific verb and resource: 'List time-off requests overlapping a date range', with optional filters named. It clearly communicates the tool's function, though it does not explicitly differentiate it from sibling tools like bamboohr_whos_out or bamboohr_vacation_overview.

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 date-range and filter language imply when the tool is appropriate, but there is no explicit guidance on when to choose this over sibling tools. It does not state exclusions or point to alternatives such as who's-out or balance tools.

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