time_and_a_half

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

With no annotations provided, the description carries the burden of behavioral disclosure. It states that the tool 'calculates' something, implying a non-mutating, read-only operation. However, it does not describe the return format (e.g., whether a single value or two values are returned) or any edge-case behavior, leaving some ambiguity.

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 concise and front-loaded with the main purpose. The second sentence includes a link to an interactive calculator, which is useful but not essential for an API agent. No wasted words, though the link could be seen as extraneous.

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 two-parameter calculator with no output schema, the description adequately states the inputs and the outputs (rate and total pay). It lacks details about output structure or edge cases, but given the tool's low complexity, it is reasonably complete.

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?

The description mentions 'hourly rate' and 'overtime hours,' which map directly to the schema's `hourlyRate` and `overtimeHours`. Since the schema has 0% description coverage, this naming helps clarify the parameters' roles, but the description adds little beyond the parameter names themselves, such as units or calculation details.

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 explicitly states 'Calculate a time-and-a-half (1.5x) overtime rate and total overtime pay from an hourly rate and overtime hours,' providing a specific verb and resource. It clearly distinguishes this tool from the sibling 'calculate_work_hours' by focusing on overtime calculation rather than general work hours.

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 description offers no explicit guidance on when to use this tool versus the sibling 'calculate_work_hours'. It does not mention alternatives, exclusions, or prerequisites. The intended use is only implied by the tool's name and the description of its calculation.

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