brc_list_customers

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

No annotations are provided, and the description does not disclose any behavioral traits such as pagination, filtering support (though params imply it), permissions, or side effects. The agent has no insight into expected behavior beyond the minimal description.

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 extremely terse (one short sentence). It fails to front-load key information that would help the agent decide to use this tool. Important details like default sorting or pagination are omitted, making it under-specified rather than concise.

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?

Given the complexity (7 parameters, no output schema, no annotations), the description is woefully incomplete. It does not mention return format, pagination behavior, or filtering capabilities. The agent cannot confidently invoke this tool based solely on the description.

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?

With only 43% schema description coverage, the description adds no value to parameter understanding. While some parameters have schema descriptions (filter, orderBy, companyName), the description does not explain any parameters, so the agent must rely solely on the schema.

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 'Lists BRC customers.' clearly states what the tool does (lists customers), but it does not distinguish it from the sibling tool 'brc_list_customers_without_dormant'. The agent must infer that this tool lists all customers, including dormant ones, which is not explicit.

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 provided on when to use this tool versus alternatives like 'brc_list_customers_without_dormant' or other list tools. There is no mention of prerequisites or contexts in which this tool is appropriate.

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