calculate_overtime_pay_fr

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

No annotations are provided, so the description must fully disclose behavior. It correctly indicates the tool is a calculation without side effects, and the return values are listed. It does not contradict any hidden behaviors, and for a computational tool, this is sufficient.

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 extremely concise — two sentences that cover the purpose, rates, threshold, return fields, and a reference to related tools. No extraneous 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?

An output schema exists (has output schema: true), so the description is not required to detail return values, but it does list them for quick reference. The description covers the core purpose and parameters adequately for a simple calculation tool, leaving no critical gaps.

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 input schema already has descriptions for both parameters (base_hourly_rate and overtime_hours), achieving 100% coverage. The description adds context about the overtime rates and threshold, which helps understand how overtime_hours is used, but it does not add new parameter-level details beyond the schema.

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 clearly states the tool calculates French overtime pay, specifying the rates (+25% for first 8h, +50% beyond) and the weekly threshold of 35h. It also lists the return fields, making the purpose unambiguous.

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 mentions a related resource ('temps-rh' calculators via list_bundles) but does not explicitly state when to use this tool versus alternatives. The threshold and rates imply use for French overtime, but no exclusion criteria or context for when not to use it is provided.

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