calculate_swiss_income_tax

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

With no annotations provided, the description carries full burden. It discloses that the tool performs a read-only computation (no side effects) and lists return fields, giving insight into behavior. It does not mention rate limits or prerequisites, but is sufficient for a tax calculator.

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 two sentences, front-loaded with purpose and return fields, and ends with a helpful pointer to related tools. Every word earns its place with no fluff.

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 presence of an output schema (not shown), the description adequately highlights key return fields. Parameter complexity is low, and the description provides enough context for the tool's functionality. Could improve by fully listing return fields or mentioning the tax year.

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 input schema covers both parameters with descriptions (100% coverage). The description adds minimal extra meaning beyond the schema, only implying the canton parameter affects the cantonal tax estimate. The return field list provides context but does not elaborate on parameters.

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 calculates Swiss income tax, specifically federal plus estimated cantonal tax. It uses a specific verb 'Calculate' and resource 'Swiss income tax', and distinguishes from many sibling income tax calculators for other countries.

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 usage for Swiss income tax calculation and directs users to 'list_bundles' for related 'finance-suisse' calculators, providing context for alternatives. However, it lacks explicit exclusions or when-not-to-use guidance.

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