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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds that results are company-scoped and include category identifiers, which is useful context, but it does not disclose pagination behavior, rate limits, or how large result sets are handled.

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 one short sentence with no filler or repetition. It states the core behavior immediately and earns its place.

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 8 parameters, no output schema, and many similar VAT-related siblings, the description is too thin. It does not explain when to choose this over list_vat_categories or process_vat_category_rates, and it leaves pagination/filtering behavior unclear. The detailed connectionRef schema description helps, but the tool-level context is incomplete.

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 description coverage is only 50%, and the description does not compensate for undocumented parameters. top, page, skip, and pageSize lack explanations, and the description adds no meaning beyond the schema for companyName or connectionRef. An agent must rely on parameter names and the schema's partial descriptions.

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 action ('Returns') and resource ('company VAT rates and their associated category identifiers'), so an agent knows what data comes back. However, it does not distinguish this from sibling tools like brc_list_vat_categories or brc_list_vat_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?

No guidance is given on when to use this tool instead of alternatives such as brc_list_vat_categories, brc_list_vat_types, or brc_process_vat_category_rates. The description only states what it returns, leaving the invocation decision entirely to inference.

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