configure_vat_mode

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

With no annotations provided, the description must fully disclose behavior. It says 'Fournit les URLs Dolibarr' (provides Dolibarr URLs), which suggests the tool returns URLs or a guide rather than directly changing settings, but this is ambiguous given the tool name 'configure_vat_mode'. It does not mention side effects, required permissions, or the nature of the response.

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?

The description is very short (two sentences), but this conciseness comes at the cost of essential information. It front-loads the purpose but omits parameter semantics and behavioral details. It could be expanded to include parameter explanations while remaining concise and well-structured.

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 no annotations, no output schema, and only a minimal description, the tool is significantly under-specified. The agent learns only that the tool relates to VAT mode and provides Dolibarr URLs, but it lacks context on what inputs are needed, what outputs to expect, and how this fits with other configuration tools. The low complexity suggests the description could easily be more complete.

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?

The input schema contains 4 string parameters (buy_product, buy_service, sell_product, sell_service) with no descriptions and 0% schema coverage. The description does not explain these parameters or how they relate to VAT mode configuration, leaving the agent completely in the dark about what values to provide.

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 tool is a guide for configuring VAT mode ('mode TVA (debits/encaissements)') and that it provides Dolibarr URLs. This names a specific resource and action, distinguishing it from other configuration tools. However, the French phrasing may slightly obscure the exact function for non-French speakers, and it does not explicitly contrast with sibling tools.

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?

No explicit guidance is given on when to use this tool instead of other configuration tools like configure_fiscal_year or configure_invoice_numbering. The description implies it is for VAT mode configuration, but it offers no context on prerequisites, scenarios, or alternatives, leaving the agent to infer on its own.

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