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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds genuinely new behavioral context by specifying that figures are gross/before tax, that amounts are statutory, and that us-XX means no state program (FMLA unpaid). It still doesn't say anything about output shape or assumptions such as continuous employment eligibility.

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 core verb (statutory pay + income gap) is front-loaded in a single dense sentence, then jurisdiction coverage. It is long but almost every clause carries information; the nested parenthetical scheme names are arguably more detail than an agent needs for tool selection.

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?

There is no output schema, and the description compensates by stating what is produced: statutory leave pay and the income gap versus normal gross pay. For a five-parameter, read-only calculator that is largely sufficient, though eligibility conditions and currency handling for the return values are left implicit.

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 100%, so all five parameters are already documented, making 3 the baseline. The description adds one meaningful clarification beyond the schema — that us-XX denotes no state program — but does not explain the interaction between topUp and topUpWeeks or how weeks defaults behave.

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 names a specific computation: statutory parental leave pay for a birth parent plus the income gap against normal gross pay, and enumerates the supported jurisdictions (UK SMP, IE Maternity Benefit, CA EI, QC QPIP, AU PLP, US states). Its multi-jurisdiction scope implicitly sets it apart from single-country siblings like ireland_maternity_leave_pay or quebec_qpip, but it never states that distinction explicitly.

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?

Usage is implied by the enumerated jurisdictions and the mention of an optional employer top-up, so an agent can infer this is the cross-country comparison tool. However, there is no explicit when-to-use/when-not guidance and no routing away from overlapping siblings such as canada_ei_maternity_parental, quebec_qpip or ireland_maternity_leave_pay, which cover subsets of the same ground.

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