get_employee_stats

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

Discloses key behaviors: searching by last name, computing metrics, returning a summary, caching, and disambiguation. Without annotations, this covers the safety profile well, though missing details like rate limits or missing name handling.

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?

Highly concise with four sentences, each providing distinct information. The purpose is front-loaded, and no superfluous text exists.

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?

Adequately covers the tool's logic, return value (summary and cached resource), and disambiguation. Missing error handling or exact output format are minor gaps given the simplicity of the tool.

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?

Adds meaning for the 'name' parameter (search by last name) over the schema, but 'days_back' is not explained. The description partially compensates for the 0% schema coverage.

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 the tool retrieves individual employee performance analysis across worktrays, specifying it searches by last name and computes per-worktray metrics. However, it does not explicitly distinguish itself from siblings like get_worktray_member_stats.

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?

Provides guidance on handling multiple matches with disambiguation, but does not explain when to use this tool versus alternatives or mention prerequisites.

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