calculate_belgian_vat

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

No annotations are provided, so the description bears the full burden. It discloses the exact return format ({amount_ht, amount_ttc, vat_amount, vat_rate}), which is valuable for an agent to understand outputs. It does not explicitly state that the tool is read-only, but the nature of a calculator implies no side effects.

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 sentences, no unnecessary words. Front-loaded with purpose, then return format and cross-reference. Efficiently conveys key information without fluff.

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 a simple calculator with a schema that fully describes parameters and an output schema implied by the description, the description is nearly complete. It includes a reference to related tools via list_bundles. However, it could be improved by explicitly stating that the tool is a pure calculation with no data modification.

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 description coverage is 100%, so baseline is 3. The description adds no additional parameter information beyond what the schema already provides. It does not explain the meaning of HT vs TTC, but the schema's 'mode' enumeration and descriptions suffice.

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 calculates Belgian VAT by converting between HT and TTC. The verb is specific ('Calculate'), the resource is explicitly 'Belgian VAT', and it distinguishes from sibling VAT calculators for other countries.

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 finance-belgique calculators', which implies there are related tools but does not explicitly state when to use this tool versus VAT calculators for other countries. Usage context is implied by the name but not spelled out.

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