Get sales order 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 covered. The description adds useful behavioral context by stating the module requirement and previewing the response contents, which matters because there is no output schema.

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 ends with a useful endpoint reference. The opening line 'Get sales order options.' is redundant with the title, but the rest of the description earns its place with concrete content and a prerequisite.

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?

The tool is simple: one optional parameter fully documented in the schema, annotations covering read-only behavior, and a description that explains what the response contains. No output schema is present, but the description adequately compensates by naming the returned VAT rates, ledger accounts, and VAT options.

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 has 100% description coverage for the only parameter, administration, including its enum and meaning. The description does not need to add parameter details, and it does not; baseline 3 applies because the schema fully carries the 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 the available VAT rates with their compatible ledger accounts and VAT options for creating sales orders.' It clearly distinguishes this from sibling tools like get_sales_invoice_options or get_quotation_options by anchoring it to sales orders and naming the returned data.

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 gives clear context for when to use the tool: when creating sales orders and needing VAT rates, compatible ledger accounts, and VAT options. It also includes a prerequisite, 'Requires the trade module to be active.' It does not explicitly name alternative tools or exclusions, but the context is clear enough.

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