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 behavior, rate limits, or data freshness. The agent has no information about what happens beyond the basic list action.

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 concise (one sentence), but it is under-specified. It lacks important details such as required parameters or output format. Conciseness should not sacrifice necessary information.

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 tool has 7 parameters and no output schema, the description is far from complete. It does not mention pagination, filtering, or the required 'companyName' parameter. The agent cannot adequately use this tool without additional context.

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 43% (low), but the description adds no parameter information. It fails to compensate for the missing descriptions, leaving the agent without guidance on how to use properties like 'top', 'page', 'skip', etc.

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 the verb 'Lists' and the resource 'BRC customers', which is specific and provides a clear purpose. However, it does not distinguish from sibling tools like brc_get_customer or brc_list_customers_without_dormant, but the core action is clear.

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. For example, there is no mention of how this differs from brc_list_customers_without_dormant or when to use filtering/pagination. The description lacks any context for selection.

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