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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered and the bar is lower. The description adds the legal basis and computation rule, which is genuinely useful context, but says nothing about rounding, currency of the result, or how total_monthly_wage affects the premium.

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 rule and formula are front-loaded in a single efficient sentence. The trailing link to an external web calculator is not needed for tool invocation and slightly dilutes an otherwise tight definition.

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?

With no output schema, the description should say more about the returned value, and it doesn't specify currency (implied SAR) or rounding. Otherwise, for a simple four-parameter calculation tool with full schema coverage and read-only annotations, it supplies enough to invoke correctly.

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 the schema already documents all four parameters including monthly_hours defaults and Ramadan guidance. The description's formula explains how basic_salary and overtime_hours combine, adding some meaning, but it does not clarify the role of total_monthly_wage or monthly_hours beyond what the schema states.

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 gives a specific verb and resource ('Calculate overtime pay') plus the governing rule (Saudi Labor Law Article 107) and the exact formula. It is clearly distinct from generic pay tools, though it never names a sibling such as saudi_net_salary or saudi_final_settlement to route the agent 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 only implied: the Article 107 framing signals this applies to overtime hours beyond normal working hours in Saudi Arabia. There is no statement of when to prefer this over hourly_to_salary or saudi_net_salary, and no prerequisites or exclusions are given.

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