brc_list_vat_rates

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

No annotations are provided, so the description must bear the burden of behavioral transparency. It implies read-only behavior (listing) but does not explicitly state safety, permissions, or side effects. It is adequate but lacks explicit disclosure for a tool with no 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?

Three sentences, each earning its place: purpose, structure, usage guidance. No fluff, front-loaded with the action. Exceptionally concise and well-organized.

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?

No output schema exists, so the description should help the agent understand what data will be returned. It provides strong context on how to use the rates (Sales vs Purchase) but does not describe the response fields (e.g., percentage, vatCategoryId values). Still, the usage guidance is very helpful, leaving only minor gaps.

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 has 7 parameters with 43% coverage; the description does not add meaning to any parameter except indirectly referencing vatCategoryId (which is not a parameter of this tool). It misses an opportunity to explain parameters like top, page, skip, pageSize.

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 it 'Lists BRC VAT rates' and explains the relationship to VAT categories via vatCategoryId. It distinguishes itself from the sibling tool brc_list_vat_categories by cross-referencing it, and the verb 'lists' is precise.

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?

Explicitly tells when to use a Sales VAT category rate for sales invoices/credit notes, and when not to use purchase rates even if same percentage. It also instructs to cross-reference brc_list_vat_categories to group rates by Sales vs Purchase before choosing.

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