get_employees

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

No annotations provided, but description adds useful context: batch limit of 1000 IDs, maps to POST /employee/get, and tier 'readonly-owner' indicating read-only access.

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?

Single concise sentence that front-loads the purpose and includes relevant constraints and endpoint mapping without unnecessary detail.

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?

Simple one-parameter tool with no output schema; description covers the essential behavior and limits, though it omits response format or error details.

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 has 0% description coverage, but the description clearly identifies the parameter as employee IDs and adds the critical constraint of up to 1000 IDs.

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?

Clearly states it retrieves full employee records for up to 1000 employee IDs, which distinguishes it from sibling search tools like search_employees.

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?

Implies usage when you have specific employee IDs and need full records, but does not explicitly mention alternatives like search_employees or resolve_employee_alias.

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