brc_process_vat_category_rates

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

No annotations provided, so description carries full burden. It discloses the two-step confirmation process and that passing preflight is not confirmation. However, it does not mention idempotency, authorization requirements, or whether it creates vs updates rates. The confirmation pattern is well explained.

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?

Three sentences, all essential. First sentence states purpose and endpoint. Second and third explain the critical usage pattern. No wasted words.

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?

Covers purpose and workflow well, but fails to describe the response structure after successful processing. Since there is no output schema, the description should at least mention what the response contains (e.g., success message, updated rates). Also lacks error handling or edge case info.

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 83%, so baseline is 3. The description adds value by explaining that vatCategoryRates must be a full array and clarifies the confirmWrite workflow. It also emphasizes that confirmProcess=true is required, which complements the schema's default false.

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 the tool processes VAT rates for VAT categories via a specific POST endpoint, distinguishing it from sibling list tools like brc_list_vat_rates. The verb 'processes' and resource 'VAT rates for VAT categories' provide specific intent.

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?

Provides explicit two-step workflow: first call without confirmWrite: true returns preview, then retry with confirmWrite: true only after user confirmation. Warns that preflight is not confirmation. However, it does not explicitly state when to avoid this tool (e.g., for read-only queries, use list tools).

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