Determine whether a job is on the Treasury Tipped Occupation list (Treas. Reg. § 1.224-1, final Apr 2026) for the § 224 'no tax on tips' deduction. Fuzzy-matches the job name; returns the official listing (name, TTC code, category) or a definitive 'not listed'.
| Name | Required | Description | Default |
|---|---|---|---|
| job | Yes | e.g. "bartender", "software engineer", "DJ" |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses the fuzzy-matching nature and the return value (official listing or 'not listed'). It does not mention side effects or permissions, but as a read-only query, this is acceptable.
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 concise sentences. It front-loads the purpose and regulatory reference, then details the behavior. No wasted 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?
Given the low complexity (one parameter, no output schema), the description is complete. It explains the input and output sufficiently. No additional context like rate limits is expected for such a tool.
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 input schema covers 100% of parameters with examples. The description adds value by explaining fuzzy matching on the job name, which goes beyond the schema's static description.
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's function: checking if a job is on the Treasury Tipped Occupation list for the §224 deduction. It specifies the regulation, the fuzzy-matching behavior, and the output format, distinguishing it from sibling tools that focus on calculations or other lookups.
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 explains when to use the tool (to determine tip deduction eligibility) and implies it's a lookup. It does not explicitly mention when not to use it or list alternatives, but the context of sibling tools provides implicit guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: calculate_tax handles individuals, calculate_business_tax handles entities, calculate_fiduciary_tax handles estates/trusts, compute_return produces the complete federal return, compute_state_return handles state returns, and the remaining tools cover specific lookups (parameters, rules, facts, dependencies, cliffs, tipped occupations) or verification. Even with overlapping domains (explain_rule, lookup_tax_parameter, search_tax_rules, verify_fact, verify_tax_claim), their roles are sharply delineated.
Tool names follow a clear pattern: compute_return, compute_state_return, calculate_tax, calculate_business_tax, calculate_fiduciary_tax, determine_dependent, explain_rule, find_tax_cliffs, is_tipped_occupation, list_input_facts, lookup_tax_parameter, search_tax_rules, verify_fact, verify_tax_claim. Most use verb_noun (calculate_tax, lookup_tax_parameter, search_tax_rules, verify_fact). Minor deviations: compare_filing_statuses and compute_return use adjective/noun phrases rather than verb_noun, but they're still readable and follow the 'compute/calculate' theme.
15 tools is well-scoped for a comprehensive tax computation server. Each tool covers a distinct aspect of tax law (federal individual, business, fiduciary, state returns, dependency, rule lookup, parameter lookup, validation, cliff detection, fact verification, search). No tool feels redundant, and the count supports the ambitious scope without bloating.
The tool surface covers the full tax workflow: input discovery (list_input_facts), computation (calculate_tax, calculate_business_tax, calculate_fiduciary_tax, compute_return, compute_state_return), dependency determination (determine_dependent), rule/parameter lookup (explain_rule, lookup_tax_parameter, search_tax_rules), verification (verify_fact, verify_tax_claim), and specialized analysis (find_tax_cliffs, is_tipped_occupation, compare_filing_statuses). There's no obvious gap; the only potential missing feature is payroll tax computation, but that's outside the stated domain of income tax.
