calculate_capital_payment_tax

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

Discloses that capital withdrawals are taxed separately at reduced rate by canton, but lacks details on other behavioral traits (e.g., how defaults are applied, error handling, or output structure). Since annotations are absent, description carries full burden but falls short.

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?

Extremely concise and front-loaded: defines purpose in first sentence, then adds a key usage hint. Every sentence provides value with no redundancy.

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 11 parameters, 3 required, and output schema present, the description is too sparse. It omits explanations for most parameters and does not guide the agent on how to use defaults or interpret results.

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?

Only location parameter is given additional meaning (ranking behavior). With schema coverage at 36%, most parameters (top, gender, capital, etc.) are left unexplained, failing to compensate for low coverage.

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?

Description clearly states it calculates tax on lump-sum payouts from pillar 2 or 3a, using specific verbs and resource. It also hints at ranking behavior, distinguishing it from sibling tools like calculate_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?

Provides guidance on using location values 'capitals' or 'switzerland' for ranking vs. single computation, but does not explicitly state when to use this tool over alternatives like plan_capital_withdrawals or calculate_tax.

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