calculate_swiss_lpp

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

With no annotations, description only discloses return format ({eligible, note}), but omits traits like idempotency, absence of side effects, or calculation method details. Adequate for a simple calculation tool.

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?

Two concise sentences with front-loaded purpose, no redundant information, and a helpful pointer to related tools.

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 simplicity (2 params, simple output), description covers purpose, return fields, and related tools. However, lacks details on calculation methodology or error conditions, which could be useful.

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 both parameters described; description adds 'by age bracket' which reinforces age parameter but does not significantly enhance understanding beyond schema.

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 occupational pension contributions by age bracket, with specific resource 'LPP / 2e pilier', and implicitly distinguishes from sibling tools like calculate_swiss_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?

Minimal guidance: hints at related calculators via 'See list_bundles', but does not explain when to use this tool versus alternatives or provide exclusion criteria.

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