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

With no annotations at all, the description carries the full load; it does disclose the return contents (breakdown, rule version, official sources), which matters because no output schema exists. It says nothing about failure behavior for unsupported countries, whether computation is side-effect free, or any rate/versioning constraints beyond the presence of a rule version.

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?

It is a single front-loaded sentence, which is good, but roughly half its length is a 35-code country list duplicated verbatim from the enum — text that earns nothing. The substantive part (what it computes and what it returns) sits on either side of that 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 two-required-param calculator with a nested free-form `options` object and no output schema, the description covers the output side acceptably but leaves the options object opaque and gives no guidance on unsupported-country behavior. Adequate but with clear gaps for a tool whose correctness depends on country-specific inputs.

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 67%, and the description's only parameter-adjacent content is re-listing the same country codes already present in the enum, which is pure repetition. The critical gross-period distinction (annual for us/in, monthly elsewhere) and the country-specific `options` bag are left entirely to the schema, so the description adds no meaning beyond it.

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?

"Gross-to-net payroll" plus the enumerated outputs (take-home pay, income tax, statutory contributions) gives a precise verb-and-resource framing that an agent can distinguish from an employer-cost calculation. It does not name the sibling tool explicitly, so differentiation is inferred rather than stated.

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 phrase "for a salary in a supported country" and the country list; there is no explicit when-to-use, when-not-to-use, or pointer to calculate_employer_cost for the employer-side figure. The agent must infer the boundary between this tool and its sibling.

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