delete_vat_type

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

The destructiveHint annotation already declares this as a destructive operation, so the description's only job is to add context — and it adds none. It does not say whether deletion is permanent, what happens to documents referencing the VAT rate, or what error occurs if the rate is in use. For a destructive mutation this is a significant gap, though it does not contradict the annotation.

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?

A single short, front-loaded sentence with no filler. It is efficient, though the brevity contributes to the under-specification noted elsewhere.

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 destructive tool with no output schema and a required undocumented identifier, the description should cover irreversibility and referential constraints. It covers none of this, so an agent has no basis for judging the consequences of a successful call.

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 50%: company_id is documented in the schema with its default resolution, but the required 'id' has no description. The description never clarifies that 'id' is the VAT type identifier nor relates it to list_vat_types/get_vat_type, leaving half the parameters unexplained in both places.

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?

Names a specific verb (Elimina) and resource (aliquota IVA / natura di esenzione), which tells an agent exactly what is removed. It does not differentiate itself from the sibling delete/update tools by name, but the resource is unambiguous.

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?

There is no guidance on when to delete versus deactivate or update via update_vat_type, and no mention of prerequisites such as whether the rate must be unused. The intended usage is only inferable from the tool name.

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