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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds what data is returned but does not disclose other behavioral traits such as pagination, rate limits, or required permissions, which are not covered by 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?

The description is a single, efficient sentence with no redundant or filler content. It conveys the essential purpose and output fields in a well-structured manner.

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 read-only tool with annotated safety, the description adequately covers the tool's function and data content. The presence of an output schema further reduces the burden of describing return values. Slightly higher than minimum because it clarifies the scope of the directory query.

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?

Both parameters are fully documented in the schema with clear descriptions ('BambooHR API key', 'BambooHR subdomain'), achieving 100% schema coverage. The description adds no parameter-specific detail, so baseline of 3 is appropriate.

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 clearly states the tool fetches the 'complete employee directory' and enumerates specific data types (names, titles, departments, contact info, manager assignments). This distinguishes it from sibling tools like get_employee (single employee) and list_employees (likely a simpler list) by emphasizing 'complete' and 'all staff.'

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 implies usage for retrieving comprehensive employee directory data but does not explicitly state when to use this tool over alternatives. No exclusions or comparisons to siblings are given, so guidance is implied rather than explicit.

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