brc_get_company_processing_settings

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

Discloses that the tool is read-only and changes must be made in Big Red Cloud, which is crucial behavioral information. Since no annotations are provided, the description adequately covers transparency for a read operation.

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?

Two concise, front-loaded sentences with no wasteful content. Every sentence adds value.

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, usage context, and behavioral constraints adequately for a read tool. Lacks description of return structure, but without an output schema, it still provides sufficient context for an agent to use it correctly.

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 100% with detailed parameter descriptions, so the tool description adds minimal new meaning beyond usage context. Baseline 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?

Clearly states it reads BRC company processing/options settings and lists specific areas affected (VAT, cash receipts, etc.). Distinguishes from siblings by its focus on processing settings, though not explicitly compared to similar get_company_* tools.

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 advises using this before VAT-sensitive write workflows, providing a clear context for when to employ this tool. Does not mention when not to use or alternatives, but the context is helpful.

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