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

The annotations already mark the tool as read-only and idempotent, and the description adds meaningful behavioral context: it uses per-country effective-rate presets shared with compare_contract, all of which are overridable, and it explicitly labels the result as an estimate, not tax advice. This gives the agent important caveats without contradicting the annotations.

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 two compact sentences with no filler. The main computation is front-loaded, followed by the preset/override detail and a necessary disclaimer, each earning 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?

For a calculator with an output schema, the description sufficiently covers the input domain, method, and caveats. The only minor gap is that it does not explicitly spell out currency assumptions or the fact that desiredNet is required, though the schema covers those. Overall it is complete enough for correct invocation.

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 high at 88%, so the baseline is 3, but the description adds value by explaining that the country parameter uses the same overridable presets as compare_contract, which compensates for the one parameter with no schema description. It also maps the core inputs ('taxes, self-paid health insurance, weeks off, and billable utilization') to the relevant parameters, clarifying how the rate is derived.

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 clearly identifies the tool as a calculator that takes a desired annual net income and produces freelance hourly and day rates, while naming the main input factors (taxes, health insurance, weeks off, utilization). This is a specific verb+resource combination and it reads distinctly from the sibling tools, none of which compute a required rate from net income.

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?

The scenario is clear: use this when you need to compute a required freelance rate from a target net income. It does not explicitly list when-not-to-use or name an alternative, but the context strongly implies the intended use case, and the mention of compare_contract provides a related point of reference.

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