calculate_senegalese_vat

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

No annotations provided, description adds that it returns HT, TTC, tax amount, but does not disclose any behavioral constraints like synchronous execution or data persistence. Since it's a simple calculation, the behavior is adequately implied.

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, front-loaded with main purpose. Some redundancy (inputs/outputs also in schema). Efficient but could be slightly more concise.

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 low complexity and rich schema (output schema exists), description is sufficient. It adds country context and reference to bundle. Could mention that rate can be customized.

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%, description merely restates inputs 'amount, mode (ht/ttc)'. No additional parameter semantics 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?

Clear verb 'Compute' with specific resource 'Senegalese VAT (TVA)'. Mentions standard rate 18%. Distinguishes from siblings by country and references bundle for related calculators.

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 usage context 'Use for invoicing in Senegal'. Points to list_bundles for alternative calculators, but does not explicitly state when not to use.

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