calculate_uk_income_tax

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

No annotations are provided, so the description bears the full burden. It discloses the calculation method (HMRC brackets, personal allowance taper) and the output structure (keys like gross_income, personal_allowance, etc.). However, it omits details on edge cases, assumption, or limitations (e.g., no special allowances).

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?

Two sentences, no redundancy. The first sentence conveys the core functionality, and the second provides a pointer to related tools. Every word is purposeful.

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?

Given the simplicity of the tool (one parameter, no nested objects, output schema exists), the description is largely complete. It explains the calculation method and lists output keys. It could be improved by noting potential limitations or assumptions, but overall it provides sufficient context.

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?

The schema already fully describes the single parameter 'income' with 'Annual gross income in GBP'. The description adds no additional semantic value beyond the schema, so it meets the baseline expectation but does not exceed 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?

The description clearly states the tool calculates UK income tax for a specific tax year using HMRC brackets and personal allowance taper. It explicitly names the resource (UK income tax), the verb (calculate), and the method. It distinguishes from sibling tax calculators by specifying 'UK' and referencing related bundles.

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 description implies the tool is for calculating UK income tax but does not explicitly state when not to use it or mention alternatives. The reference to 'list_bundles' for related calculators provides some contextual guidance, but no clear exclusion criteria are given.

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