Who's out

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description does not need to repeat safety traits. It adds valuable behavioral detail by describing the output structure (each entry has type 'timeOff' or 'holiday' with specific fields) and the default date range. This goes beyond annotations and helps the agent understand what to expect.

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 concise sentences: purpose, defaults, and output format. No redundant information, front-loaded with the core action. Every sentence adds value.

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 read-only list tool with two optional parameters and no output schema, the description covers the essential details: what it lists, the default range, and the shape of entries. No missing information is needed for an agent to call it 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 description coverage is 100%, with both 'start' and 'end' documented with defaults and formats. The description does not add new parameter semantics beyond what the schema already provides; it repeats the default behavior in prose. Baseline 3 is appropriate since the schema carries the semantic load.

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') and a clear resource: employees out of office and company holidays. It distinguishes itself from siblings like bamboohr_list_employees (all employees) and bamboohr_company_holidays (holidays only) by combining both into a single view. The purpose is unambiguous.

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 provides context (date range, defaults) but does not explicitly state when to use this tool versus alternatives. It does not mention exclusions or recommend sibling tools for specific needs, leaving some inference to the agent. However, the combined nature is implied by the title and content.

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