calculate_swiss_wealth_tax

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

No annotations are present, so the description must disclose behavioral traits. It describes a calculation with a return object but does not mention safety (read-only), side effects, or authentication needs. The return object structure is a positive but insufficient without behavioral context.

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-sentence description is extremely concise, front-loaded with purpose and return format, and the second sentence adds useful cross-reference. No redundancies.

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?

The tool has an output schema, so description needn't explain return values, yet it does. It also hints at sibling tools. For a simple calculator, enough context is provided for an AI to invoke correctly. Minor gap: no mention of validation limits for net_wealth (e.g., max reasonable value).

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?

Input schema provides full descriptions for both parameters (100% coverage). The description adds no extra parameter semantics, but it lists the return object, which is helpful but not required. Baseline of 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 verb 'Calculate', resource 'Swiss wealth tax', and scope 'by canton'. It lists exact return fields, making the purpose unambiguous and distinct 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?

The description mentions 'See list_bundles for related calculators', hinting at related tools but not explicit when/why to use this tool instead. No prerequisites or exclusions are provided, leaving guidance to implicit context.

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