get_employee_hours

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

No annotations are provided, so the description carries full burden. It states it flags overtime, implying a read-only behavior with additional processing. No mention of side effects, permissions, or data limits. For a simple retrieval, this is adequate but not exemplary.

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 sentences, no redundant information. Every word serves a purpose. The description is front-loaded with the core action and immediately provides a practical use case.

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?

Given the tool has 2 parameters and no output schema, the description covers the basic purpose and a use case. However, it lacks details on return format, pagination, or behavior with empty employee_name. It is minimally adequate but could be more complete given the context.

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 50% (employee_name described, days only has default). The tool description adds no additional parameter meaning; it does not explain the 'days' parameter or clarify input formats. With low coverage, the description fails to compensate.

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 hours and pay and flags overtime. The verb 'Get' and resource 'employee hours' are specific. While it doesn't explicitly contrast with siblings, its focus on individual employee hours and overtime distinguishes it from broader summary tools like 'get_labor_summary'.

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 a specific use case: 'Use to check if anyone is approaching overtime threshold.' However, it lacks guidance on when not to use it or mention of alternative tools (e.g., 'get_labor_summary' for aggregated data). The usage hint is present but incomplete.

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