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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is fully covered. The description adds the useful signal that the output is a gross pay figure in the target country (shown via two sample results), but says nothing about assumptions, tax-year, or whether allowances are treated as taxable.

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?

Two short sentences plus a reference URL: a concrete worked example first, then the scope statement. Nothing is padded and the most informative element is front-loaded.

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 7-parameter tool with no output schema, the description conveys the input scenario and the shape of the answer, but never explains the conditional parameter structure (state vs. province vs. provRate depending on the country) or what the returned figure includes. Adequate but leaves real 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?

Schema description coverage is 100%, so every parameter including provRate, stateRate and the salary/allowance definition is already documented in the schema; the description only echoes 'salary' and 'state' through its example. Baseline 3 applies — it neither compensates for nor adds to the structured data.

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 concrete transformation — matching a tax-free Gulf monthly salary with the gross pay needed in the US, UK or Canada — and illustrates it with real numbers (AED 25,000 → $103,565 in Texas). The resource and direction of the conversion are unambiguous, though it never names the adjacent tools (salary_calculator, take_home_pay_calculator, income_tax_calculator) that an agent might confuse it with.

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 example shows the intended scenario (someone earning a Gulf package wanting a Western equivalent), but there is no explicit 'use this when…' statement, no exclusions, and no routing to alternatives such as income_tax_calculator for non-Gulf comparisons.

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