calculate_salary_restructuring

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

Annotations already convey readOnlyHint=true and idempotentHint=true, so the safe, non-mutating nature is covered. The description adds that it returns a standard envelope with tax-optimized structure and deductions, but it does not disclose much behavior beyond what the annotations and output schema already provide. No contradiction exists.

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 front-loaded with the purpose and usage context, then organized into Args and Returns sections. It is reasonably sized for nine parameters, though the Args list duplicates parameter details already present in the schema.

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 rich input schema, annotations, and output schema, the description supplies the missing context: when to use the tool and what the result conceptually contains. All parameters are present and defaults/constraints are handled by the schema, so the description is complete for its scope.

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 the input schema already documents every parameter. The description's Args section largely repeats the schema's text and adds no new constraints, formats, or usage semantics beyond what the schema 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?

The description clearly states a specific verb and resource: it calculates salary restructuring options for tax optimization. It is readily distinguishable from sibling calculators like calculate_income_tax or calculate_hra_exemption because it targets the overall salary structure and CTC planning, not a single tax computation.

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 gives explicit use context: 'Use when advising employees on tax-efficient salary structures, comparing restructuring options, or planning CTC optimization.' It does not explicitly list when not to use it or name an alternative sibling tool, but the context is clear enough for an agent to select it.

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