calculate_swiss_salary

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

The description lists some return fields (e.g., avs_ai_apg_5_3pct, net_monthly), providing basic transparency. However, it does not disclose assumptions, precision, or limitations of the estimation, and no annotations are provided to compensate.

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 with two sentences, front-loaded with the tool's purpose, and includes a pointer to related calculators. No wasted words.

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 complexity of Swiss salary calculations, the description lists several deduction fields and points to an output schema. The mention of list_bundles provides context for related tools. It is reasonably complete for a well-structured tool with an output schema.

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 coverage is 100% with one parameter described in the schema as 'Gross monthly salary in CHF'. The description adds no further detail, so the schema carries the semantic burden adequately.

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 converts Swiss gross monthly salary to estimated net salary, specifying the resource (Swiss salary) and the action (convert). It distinguishes from sibling salary calculators by explicitly mentioning 'Swiss'.

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 mentions related calculators via 'list_bundles', suggesting alternatives, but does not explicitly state when to use this tool versus other salary calculators or when not to use it.

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