Self-Employment (1099) Tax Calculator

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

No annotations provided, so description carries full burden. It discloses tax year (2026), source (Tax Foundation & IRS), and adds disclaimer ('estimates, not tax advice'). It also includes example input and explains the tax breakdown, making behavior transparent.

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?

Description is a single paragraph that packs dense information (tax breakdown, formula, example, year, source) without being overly verbose. Could potentially be split for readability, but it is concise and front-loaded.

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 complexity (4 parameters, multiple tax calculations, optional state tax), the description covers the main functionality well. No output schema, but it mentions quarterly estimated-payment figure. Disclaimers and example enhance completeness.

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 baseline is 3. The description does not add extra parameter-level information beyond what the schema already provides (e.g., enum descriptions). Schema already explains netProfit, filingStatus, state, otherIncome clearly.

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?

Description clearly states it computes Schedule SE self-employment tax (with breakdown), Additional Medicare surtax, federal income tax, optional state tax, and quarterly estimated payments. It distinguishes from sibling tools like us_take_home_pay and capital_gains_tax by specificity.

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?

Description explains the tool computes self-employment taxes and when it's appropriate. It lacks explicit exclusions or comparisons to siblings, but the purpose is clear and context signals provide sibling names. The example input helps understand usage.

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