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

No annotations are provided, so the description carries the burden. It discloses that this is an estimate and not the IRS tracker, and gives the formula. It does not mention output sign conventions, tax year, or that results depend entirely on user-provided inputs.

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 with no filler. The core purpose and formula are front-loaded, and the clarifying exclusion is placed second. Every sentence earns 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 an 8-parameter calculator with no output schema, the description gives the essential formula, scope, and a key exclusion. It is slightly incomplete because it does not state the output sign convention or clarify behavior when optional state parameters are omitted, but it is sufficient 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 100%, so the baseline is 3. The description adds meaningful parameter relationships by explaining 'tax owed minus withholding minus credits' and the federal/state scope, which helps an agent understand how grossIncome, federalWithheld, stateWithheld, and credits interact.

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 uses a specific verb ('Estimate') and resource ('US tax refund or balance due'), and defines the calculation formula. It clearly distinguishes itself from the IRS refund tracker, making its purpose unambiguous.

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 provides clear context: use before filing to estimate refund or balance due, and explicitly excludes the IRS refund tracker. However, it does not name sibling alternatives like calculate_income_tax or explain when to prefer those.

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