calculate_hra_exemption

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

Annotations already declare readOnlyHint and idempotentHint as true, indicating a safe, read-only operation. The description adds value by explaining the internal logic ('compares three conditions and takes minimum'), providing useful behavioral insight beyond annotations. No contradiction.

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 extremely concise: three sentences with no wasted words. The first sentence states the core purpose, and subsequent sentences add usage and logic. 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 tool's complexity (5 parameters, 3 required) and the presence of an output schema, the description is complete. It covers purpose, usage context, internal logic, and is self-contained. No gaps remain.

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 every parameter already has a clear description in the schema. The tool description adds minimal extra meaning (e.g., 'compares three conditions' gives context), but does not significantly enhance parameter understanding beyond the schema. Baseline 3 is appropriate.

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: 'Calculate House Rent Allowance (HRA) exemption under Section 10(13A).' It uses a specific verb-resource combination and distinguishes from sibling calculation tools like calculate_advance_tax and calculate_income_tax.

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 provides usage context: 'Use when computing tax-exempt HRA component for salary structuring or income tax filing.' It also notes the tool compares three conditions and takes the minimum, but does not explicitly mention when not to use or list alternatives, which would elevate to a 5.

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