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

The annotations declare readOnlyHint=true and destructiveHint=false, but the description adds no behavioral nuance beyond the obvious read operation. It does not mention pagination, dormant-customer behavior, company-context requirements, or response characteristics, and there is no output schema to fill that gap.

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. It is concise and readable, though its brevity comes at the cost of important accompanying guidance.

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, a required companyName, and a very large sibling list, a single sentence is not enough. Missing details such as pagination behavior, connectionRef reuse, required company context, and how this differs from the dormant-customer list variant leave the agent underinformed.

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?

The description contributes nothing about parameters; it simply names the resource. Schema description coverage is only 50%, and the description does not compensate for the unexplained pagination and filter params, nor does it clarify the required companyName context.

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 names the operation and target resource: 'Lists BRC customers.' However, it does not differentiate this tool from closely related siblings such as brc_list_customers_without_dormant or brc_get_customer, so it stops short of the top rating.

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 gives no direction about when to use this tool instead of alternatives like brc_list_customers_without_dormant, brc_get_customer, or brc_batch_customers. The expected usage is only implied by the tool name and title.

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