bamboohr_list_employeesRetrieve current employee records with names, titles, departments, and supervisors to identify people and use their IDs for time-off requests.
List current employees from the BambooHR directory with id, name, job title, department, division, location, supervisor and work email. Use the id with the balance and request tools.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v3.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish readOnlyHint, idempotentHint, and non-destructive behavior, so the bar is lower. The description adds meaningful behavioral context by specifying the exact field set returned and signaling that the output is a directory listing of current employees. It does not mention pagination or sorting, but for a zero-parameter list tool these are minor gaps.
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 focused sentences, with the core action and scope front-loaded and the downstream usage hint placed second. Every sentence earns its place with no redundant phrasing.
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 simple, zero-parameter listing tool, the description is complete: it states what is listed, which fields are returned, and how the returned IDs should be used. The annotations cover safety and idempotency, so nothing essential for correct invocation is missing.
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?
The tool has zero parameters, so the description does not need to explain parameter behavior; the baseline of 4 applies. The field list in the description compensates for the absence of an output schema by indicating what the returned data will contain.
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 states a specific verb ('List'), a precise resource ('current employees from the BambooHR directory'), and enumerates the returned fields (id, name, job title, department, division, location, supervisor, work email). It clearly differentiates from sibling tools like get_employee and list_users by focusing on the employee directory listing.
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 gives clear context: this is for obtaining current employees and their IDs for downstream use with 'balance and request tools.' It does not explicitly state when to avoid this tool in favor of a sibling such as get_employee, but the 'current employees' scope and the downstream ID guidance provide usable direction.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.