Get quotation options

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the safety profile is covered. The description adds the endpoint and the specific contents returned, but it does not add deeper behavioral context such as response shape, authentication needs, or prerequisites.

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 compact and front-loaded with the key information about VAT rates and ledger accounts. However, the opening sentence simply repeats the tool title, which is slightly redundant but not damaging.

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?

With no output schema, the description does a reasonable job of explaining what the tool returns by naming VAT rates, compatible ledger accounts, and VAT options. It lacks detail on response format or errors, but the endpoint is simple, has no required parameters, and annotations cover the safety profile.

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 schema provides 100% coverage for the single 'administration' parameter, including an enum and a clear description. The tool description does not need to repeat this and adds no additional parameter semantics.

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 ('Get quotation options') and elaborates on the exact contents: VAT rates, compatible ledger accounts, and VAT options for creating quotations. This clearly distinguishes it from sibling get_*_options tools for other document types.

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 phrase 'for creating quotations' implies the intended use case, but the description gives no explicit guidance on when to choose this over alternatives like get_sales_invoice_options or list_vat_options. No exclusions or alternative routing are mentioned.

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