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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so safety behavior is covered. The description adds valuable domain behavior by disclosing the calculation rule (21 days then 30 under the 2021 law) and an example output, though it does not describe the exact return format.

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 three short sentences, front-loaded with a concrete example and then the statutory rule. Every sentence contributes to understanding the calculation, with no redundant filler.

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 calculator with full schema coverage, no required parameters, and no output schema, the description supplies the formula, jurisdiction, and an example result. It is nearly complete, though it could explicitly state that the tool returns the gratuity amount.

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 defaults, formats, and constraints. The description's example implicitly reinforces basic salary and years of service but adds no parameter-level syntax or meaning 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 states a specific UAE end-of-service gratuity calculation, includes the statutory formula (21 days for first 5 years, then 30), and names the governing 2021 law. It distinguishes itself from sibling country-specific and GCC gratuity tools by explicitly scoping to UAE.

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 gives clear context for when to use the tool: UAE end-of-service benefit under the 2021 law. It does not explicitly name alternatives such as gcc_gratuity_calculator or other country-specific calculators, nor state when not to use it, but the jurisdiction cue is strong.

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