Compute Tva

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

Annotations declare readOnlyHint=true, which matches the description's 'calculate' semantics (read-only computation). The description does not add behavioral traits beyond this: no mention of permissions, performance, or side effects. It adequately aligns but adds no extra value over annotations.

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 fluff. First sentence states purpose and scope; second details outputs and currency. Front-loaded and efficient.

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?

For a simple tool with one parameter and no output schema, the description covers the purpose, scope (para-hotel properties subject to VAT), outputs (collected/deductible/balance), granularity (by property, rate, quarter), and currency. It does not clarify whether it computes for all or selected properties, but given the single year parameter, it's implied. Nearly complete for the context.

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 has one integer parameter 'year' with 0% description coverage. The description mentions 'sur une année donnée' (for a given year), providing basic semantic meaning. However, it does not specify format (YYYY), range, or relation to other years. This is minimal compensation for the lack of schema description.

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 it calculates VAT declarations for para-hotel properties subject to VAT regime for a given year. It specifies output components (VAT collected, deductible, balance) and breakdown by property, rate, and quarter. The verb 'calculate' and resource 'VAT declaration' are specific and unique among siblings like compute_depreciation or compute_fiscal_year.

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 on when to use this tool versus alternatives. The description does not mention conditions, prerequisites, or cases where another tool (e.g., compute_fiscal_year) would be more appropriate. Implicit usage for VAT queries is clear, but no comparative advice.

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