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 adds genuine behavioral context the annotations do not: the response contains per-quarter running totals with each update deadline, monthly and weekly amounts, and a first payment on account. It does not say the figures are estimates or that nothing is filed or persisted, which would have made this a 5.

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 dense sentence that front-loads the purpose and then lists outputs, with no filler. The enumerated output list makes it long but every clause carries information an agent needs to judge relevance.

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 four optional parameters and no output schema, the description does the necessary work by describing the shape of the result (tax breakdown, set-aside amounts, quarterly running totals, deadlines). Gaps remain around defaults when no parameters are supplied and the estimate-only nature of the figures, but nothing critical for correct invocation is missing.

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 the baseline is 3. The description's 'from the year's profit or each quarter's profit' reinforces the annual-vs-quarterly alternative, but that is already stated in the schema ('instead of an annual figure'), so it adds little new meaning; the student loan plan and first-year flag parameters are not elaborated on at all.

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 specific verb and resource ('plan how much to set aside for tax') and pins the scope to a sole trader under Making Tax Digital, then enumerates exactly what is computed (income tax, Class 4 NI, student loan, monthly/weekly set-aside, quarterly running totals, payment on account). That is far more specific than a sibling like estimate_self_employed_tax, but the contrast with that sibling is never made explicit.

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?

It gives clear applicability context — sole trader, Making Tax Digital — and indicates the two alternative input modes ('from the year's profit or each quarter's profit'), which is the key usage decision for this tool. It stops short of naming alternatives (e.g. estimate_self_employed_tax, get_mtd_deadlines) or saying when not to use it.

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