calculate_us_federal_tax

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

With no annotations provided, the description carries the full burden. It accurately portrays a safe read-only calculation, disclosing the tax year and standard deduction. However, it does not mention potential limitations (e.g., income types not covered) but overall is transparent enough for a calculator.

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 sentences, front-loaded with the core purpose, and efficiently includes return fields and a pointer to related tools. No unnecessary words.

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 tool with an output schema (referenced in description), the description is complete: it explains what, how, and what returns. It also hints at related tools. Minor gap: no mention of tax rules changes beyond 2026, but still adequate.

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 100% with clear parameter descriptions. The description adds context about 2026 and progressive brackets but does not elaborate further on parameters. Baseline of 3 is appropriate as schema already does the heavy lifting.

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 US federal income tax for 2026 using progressive brackets with standard deduction. This specific verb+resource combination distinguishes it from sibling tools like calculate_us_state_tax or calculate_french_income_tax.

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 only mentions 'See list_bundles for related finance-us calculators,' which provides a vague hint but no explicit guidance on when to use this tool versus alternatives. There is no indication of prerequisites or 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.