deduction_value

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

Despite no annotations, the description fully discloses behavioral traits: it sweeps a budget line, reports tax saved at each level and incremental savings, and explains the impact of progressive rates and bracket boundaries on the output.

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 concise at four sentences, front-loaded with the purpose, and efficiently uses each sentence to convey key information without 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?

Given the tool's complexity (17 parameters, output schema exists), the description covers the core functionality and output but lacks details on prerequisites, error cases, or parameter relationships, leaving some gaps for a complete understanding.

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 description adds minimal parameter context beyond mentioning the default deduction type ('pillar 3a'). With 17 parameters and only 41% schema coverage, the description should compensate for undocumented parameters but does not elaborate on required inputs like location and income1.

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 purpose: 'Measure what a deduction is actually worth to this household' and describes the action: 'Sweeps a budget line ... and reports the tax saved at each level'. It uniquely focuses on deduction value, differentiating from sibling tools like calculate_tax or list_deductions.

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 when to use the tool (to evaluate deduction value with progressive rates) but does not explicitly mention alternatives or when not to use it. It provides clear context for its application.

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