hcp_list_employees

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

Annotations already establish the tool as read-only, idempotent, and non-destructive. The description adds useful behavioral context: auto-pagination unless an explicit page is set, and the pro_ prefix used in employee IDs. This helps the agent interpret returned data correctly and contradicts nothing in 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?

Two concise sentences with no filler. The action and resource are front-loaded, and each additional clause provides useful behavior or ID-format information.

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 list tool with optional pagination parameters and an output schema, the description covers the main invocation behaviors: pagination mode and ID prefix. It could be slightly more complete by explaining page_size, but no critical information is missing for making a correct call.

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 0%, so the description must compensate for the bare integer/null parameters. It explains that explicit page disables auto-pagination, giving page meaningful behavior, but page_size semantics remain undocumented. Partial coverage with a clear gap.

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?

Description opens with 'List employees/technicians', naming the exact operation and resource. This clearly distinguishes it from sibling tools like hcp_list_leads, hcp_list_customers, and other list endpoints.

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?

No guidance is provided on when to use this tool versus alternatives, or when not to use it. The only behavioral note is about pagination, not about selection criteria or related tools.

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