get_vat_type

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

The readOnlyHint=true annotation already tells the agent this is a safe read, so the bar is lower, but the description adds no behavioral context whatsoever. 'Dettaglio completo' hints at a full-object return but there is no output schema and nothing about what fields come back, error behavior for an unknown id, or multi-company scoping.

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?

One short, front-loaded sentence with no filler or redundancy. It is efficient, though as a bare noun phrase it lacks an action verb that would make the intent unmistakable.

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 read tool with no output schema, an undocumented required id, and 50% parameter coverage, the description is too thin to let an agent invoke it confidently. It should at least state what a VAT type record contains (rate, exemption nature, codes) and what id refers to.

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 only 50%: company_id is documented in the schema, but the required id parameter carries no description anywhere. The description does not compensate — it never explains that id is the VAT type identifier, nor how the two parameters interact.

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 says it returns the complete detail of a VAT rate or exemption nature, which does identify the resource being fetched. However it just restates the name's 'get_vat_type' semantics and never names a verb, nor does it distinguish this from list_vat_types or the other vat_type siblings.

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 when-to-use guidance at all — nothing says to use this instead of list_vat_types when the numeric id is known, and no prerequisites or follow-up steps are given. The agent must infer the retrieval-by-id pattern from the tool name alone.

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