Get all VAT options

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is well covered. The description adds no additional behavioral traits such as pagination, ordering, or output format beyond the content of the response, so it neither strongly enhances nor contradicts the 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?

The description is short and front-loaded, with the essential scope in the first sentence. There is minor redundancy between 'Get all VAT options' and the expanded second sentence, and the '[VAT] GET /vat' hint is helpful but slightly extraneous.

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 read-only list tool with one optional parameter and no output schema, the description provides enough detail about the returned data categories. It could mention the response shape or pagination, but the operation is straightforward and annotations cover the safety 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?

The input schema has 100% description coverage, fully documenting the single optional 'administration' parameter and its enum. The tool description itself adds no parameter-level detail, so it does not need to compensate; the baseline of 3 applies.

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 a specific action (get a list) on a specific resource (VAT/tax rates) and details the included fields (percentages, codes, availability status). This distinguishes it from sibling list tools and invoice-specific options 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?

The description implies the tool is used to retrieve VAT rates configured for the administration, providing clear context for when to call it. However, it does not explicitly mention when not to use it or name alternatives such as get_sales_invoice_options or get_purchase_invoice_options, leaving some inference to the agent.

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