Income Tax Old Regime

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

No annotations are present, so the description carries the full behavioral burden and does not meet it. It never says the tool is a side-effect-free calculation, discloses which statutory components are modeled (cess, surcharge, rebate), or states that deduction inputs are capped internally — the schema mentions an 80C cap but the description adds nothing about output assumptions.

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?

A single front-loaded sentence with the assessment-year context included and no filler. Every clause 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?

An output schema exists, so return values need not be explained. However, with no annotations the description should confirm this is a pure, non-mutating calculation and clarify its relationship to the new-regime and compare-regimes siblings — neither is addressed.

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 all four parameters (age, gross_salary, deductions_80c, other_deductions) are already documented with defaults and caps. Baseline 3 applies; the description contributes no additional parameter meaning beyond what the schema already provides.

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?

States a specific verb ('Estimate'), resource ('income tax') and scope ('FY 2026-27 (AY 2027-28) under the OLD regime'). The regime qualifier implicitly separates it from income_tax_new_regime, but the description never names that sibling explicitly, so the differentiation is left to inference.

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?

Usage is only implied by the 'OLD regime' phrasing; there is no statement of when to choose this over income_tax_new_regime or income_tax_compare_regimes. No prerequisites, no exclusions, no pointer to the comparison tool that would obviously be relevant.

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