calculate_swiss_vat

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

No annotations provided, so description carries burden. It states it returns HT, TTC, and tax amount, and lists inputs. But does not mention any limitations, side effects, or authentication needs. Sufficient for a simple 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?

Very concise: two sentences covering purpose, use case, inputs, outputs, and related tools. 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?

Tool is simple with good schema and output schema. Description covers purpose, use case, inputs, outputs, and mentions related tools. Only minor issue with rate listing.

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%, so baseline 3. Description lists inputs and outputs but largely repeats schema. Adds minor context on output structure, but includes incorrect rate value (0) not in enum.

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?

Clearly states it computes Swiss VAT and converts between net and gross, for invoicing/expenses in Switzerland. However, description lists rate 0 which is not in schema enum, causing slight inconsistency.

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?

Specifies use for invoicing or expense reimbursements in Switzerland, but does not provide guidance on when not to use or compare to sibling tools like calculate_vat_generic. Only suggests list_bundles for related calculators.

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