vat_rates_create

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

Annotations cover readOnlyHint=false, idempotentHint=false, and destructiveHint=false. The description adds meaningful behavioral context beyond annotations: setting isDefault demotes the existing default, and the first VAT rate automatically becomes default. It does not mention duplicate handling or side effects on existing invoice lines, so not a 5.

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 four sentences, front-loaded with the core action, and every sentence adds useful information about defaults or category codes. There is no redundant or filler text.

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 create mutation with full schema coverage and annotations, the description supplies the key behavioral details: default demotion and automatic first-rate defaulting. It could mention whether duplicate rates are allowed or how companyId override interacts with the active company, but the essentials are covered.

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%, so the baseline is 3. The description adds real meaning for categoryCode by explaining common e-Factura codes and clarifies the isDefault side effect. A minor inconsistency exists: it lists AA=reduced, which is not in the schema's option list (S, Z, E, AE, K, L, O, M), and omits K, L, M.

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 states a specific verb and resource: 'Create a new VAT rate for the active company.' It clearly distinguishes creation from sibling tools like vat_rates_update, vat_rates_delete, and vat_rates_list.

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?

The purpose implies when to use the tool, but there is no explicit guidance on when to choose it over vat_rates_update or vat_category_codes_list. No alternatives or exclusions are named.

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