Employee files

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds meaningful behavioral context by stating 'Metadata only; files are not downloaded.' This clarifies that the tool will not return binary file content, which is useful beyond the structured 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 two sentences with no wasted words. It front-loads the primary action and resource, then supplements with output details and a key limitation. 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 simple one-parameter read-only tool with no output schema, the description covers the resource, output fields, and behavioral limit (no downloads). It is complete enough for an agent to call correctly, though it could optionally mention pagination or error behavior.

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 the employeeId parameter is already well documented as 'Internal employee id.' The description adds only implicit context by referring to 'an employee's record', which does not materially improve parameter understanding beyond the schema.

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 opens with the specific verb 'List' and names the exact resource ('document categories and files stored on an employee's record'), including examples of document types and the returned metadata fields. This clearly differentiates it from sibling tools like bamboohr_get_employee or bamboohr_table_rows.

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 purpose statement makes it easy to infer when to use this tool, but it never explicitly says when to choose it over alternatives or mentions conditions like 'use this when you need file metadata but not downloads'. It is adequate but relies entirely on inference.

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