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

Annotations already establish this is a safe, read-only, closed-world computation. The description adds useful context that it returns both gross hourly rate and take-home pay per hour and that results are tax-year specific, but says nothing about assumptions (UK tax regime, NI/student loan handling) beyond what the schema hints at.

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 conveys the core transformation and the key inputs without padding. It is somewhat dense but every clause earns its place.

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 usefully names the two return values (gross hourly rate, take-home pay per hour), which is exactly what an agent needs to know. It is complete enough for a read-only calculation tool, though it could note that results are UK-specific.

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 six parameters including enums are already documented. The description restates hours a week, paid weeks a year, and tax year without adding format or default semantics beyond the schema (e.g. that paidWeeksPerYear defaults to 52 is only in the schema). Baseline 3 applies.

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?

States a specific verb+resource (convert an annual salary to gross hourly rate and take-home pay per hour) with clear directionality, which implicitly distinguishes it from the reverse-direction sibling convert_hourly_rate_to_salary. It doesn't explicitly name that sibling, but the direction is unambiguous from the text.

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 by the description's scope — an agent can infer it is for salary→hourly conversion given hours/week and paid weeks/year, but there is no explicit when-to-use, when-not-to-use, or reference to the reverse tool or to calculate_contractor_day_rate. Adequate but with clear gaps.

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