optimize_deductions

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

With no annotations, the description carries the burden of disclosing behavior. It clearly explains the tool flags over-cap amounts and unused headroom, and quantifies potential tax savings. It does not mention side effects, but the language implies a read-only analysis, which is adequately 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?

The description is three sentences with no filler. Each sentence serves a distinct purpose: naming the tool's function, explaining its outputs, and stating its applicability. It is front-loaded and well-structured.

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 moderate complexity and no output schema, the description sufficiently explains the tool's return value (flags, unused headroom, quantified savings). It does not mention edge cases or behavior under the new regime, but the statement 'Applies to the OLD regime' covers the main constraint.

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 high (75%), so the schema already explains parameters well. The description adds context by clarifying that deductions apply only in the old regime and that the tool audits against caps, but it does not detail individual parameter semantics beyond the schema.

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 ('audits') and identifies the precise resource (taxpayer's Chapter VI-A deductions) and scope (against statutory caps). It clearly distinguishes itself from siblings like calculate_income_tax by focusing on optimization, not just calculation.

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 explicitly states 'Applies to the OLD regime', providing a clear contextual constraint. However, it does not name alternative tools or provide explicit 'when not to use' guidance, though this is partially implied.

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