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

Annotations already declare read-oly, non-destructive behavior, so the description does not need to repeat that. It adds the behavioral context that these settings affect VAT-sensitive accounting workflows, which is useful, but it does not explain the shape of the response or any other operational traits beyond what annotations cover.

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?

One short, front-loaded sentence with no filler. Every word earns its place, and the VAT qualifier adds meaning rather than bulk.

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 schema covers all parameters and annotations cover safety, but there is no output schema and the description does not explain what the returned settings contain or how this getter differs from the many sibling settings getters. An agent could call it for a VAT-processing question, but may not be certain it is the right choice among similar tools.

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 100%, and the parameter descriptions for companyName, includeRaw, and connectionRef are already detailed. The tool description itself adds no additional parameter semantics, so the baseline score of 3 is appropriate.

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 a specific verb and resource ('Returns company processing settings') and adds a useful qualifier about VAT-sensitive accounting workflows, so it goes beyond a tautology. It does not enumerate what the settings are or explicitly contrast with sibling getters, but the core purpose is understandable.

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 implies a context — settings relevant to VAT-sensitive workflows — but never states when to choose this tool over the many related settings tools such as brc_get_company_reference_settings or brc_list_company_settings. It provides no explicit when/when-not guidance or named alternatives.

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