calculate_federal_tax

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

With no annotations provided, the description carries full burden. It effectively discloses key behavioral traits: the tool runs locally with no data transmission (privacy/security context), and lists comprehensive calculation components (bracket breakdown, various taxes, deductions, credits). However, it doesn't specify output format or calculation methodology details.

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 efficient sentences: first establishes core purpose and scope, second adds crucial behavioral context about local execution. Every word earns its place with zero redundancy.

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 complex 16-parameter tax calculation tool with no annotations or output schema, the description provides strong purpose clarity and behavioral context. It adequately covers what the tool does and its privacy approach, though it could better explain when to use it versus sibling tools.

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%, providing detailed parameter documentation. The description adds minimal parameter semantics beyond the schema, only implying that parameters relate to the listed calculation components. Baseline 3 is appropriate when schema 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 specific action ('calculate federal income tax'), target resource ('individual taxpayer'), and scope ('supports TY2024 and TY2025'). It distinguishes from siblings by focusing exclusively on federal tax calculation rather than state taxes, credits, or other tax-related analyses.

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 usage for federal tax calculations with specific tax years, but provides no explicit guidance on when to choose this tool versus alternatives like 'calculate_total_tax' or 'calculate_eitc'. No prerequisites or exclusions are mentioned.

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