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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description usefully adds that the result includes take-home pay for a given tax year, but says nothing about rounding, currency assumptions, or how UK tax bands/Scottish rates are applied, so the added behavioural value is modest.

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?

A single front-loaded sentence that opens with the conversion and appends the tax-year take-home context; it is slightly run-on but every clause carries information and there is no 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 read-only calculator with no output schema, the description conveys both the primary output (annual salary) and the secondary output (take-home pay) and the inputs that shape them. An agent has enough to call it correctly, though it lacks caveats about tax-year defaults or regional variation.

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%, so every parameter (taxYear, hourlyRate, hoursPerWeek, studentLoanPlan, paidWeeksPerYear, scottishTaxpayer) is already documented in the schema. The description only restates hours/week, paid weeks and tax year, adding no syntax, defaults or edge-case 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 names a specific verb and resource ('convert an hourly rate to the annual salary') and states the scope of the conversion (hours/week, paid weeks/year) plus the take-home-pay output. It is clearly distinguished from the inverse sibling convert_salary_to_hourly_rate.

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 direction of the conversion, which separates it from convert_salary_to_hourly_rate, but there is no explicit when-to-use guidance or pointer to related tools like calculate_take_home_pay or calculate_pro_rata_salary. Nothing is misleading, just unstated.

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