calculate_maternity_leave_fr

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

With no annotations, the description only states it returns pre/post-birth leave days and allowance estimate. It lacks disclosure on prerequisites, limitations, or error handling, which would be important for a computation tool.

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 with two sentences plus a reference to related tools. Information is front-loaded: purpose first, then usage, then related resources. No wasted words.

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?

The description mentions return values but omits details like default behavior, processing of 'twins' parameter, and the missing 'due date' input. With an output schema present, the gap on inputs is critical and makes it incomplete.

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 coverage is 100% and already describes parameters. The description adds 'due date' as an input, which is absent from the schema, creating confusion and misleading the agent. This outweighs the redundant clarity on other parameters.

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 computes French maternity leave duration and IJSS allowance, with a specific verb and resource. It distinguishes from sibling calculators, though it mentions 'due date' which is not in the schema.

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?

It explicitly says 'Use for HR or expectant parents' and directs to related bundles, providing clear context. Lacks explicit when-not-to-use, but specificity compensates.

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