brc_list_customers_without_dormant

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

No annotations exist, so the description must disclose behavior. It fails to explain what 'dormant' means, how filtering works, pagination behavior, or any side effects. The schema includes pagination parameters (top, page, skip, pageSize) but these are not mentioned in the 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 succinct (one sentence), which is concise, but it is too brief given the tool has 7 parameters. It lacks structure to present essential information efficiently.

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 description is insufficient for a tool with 7 parameters, no output schema, and no annotations. It omits details about the return format, pagination, meaning of 'dormant', and how to use the filtering/ordering parameters. The context of the BRC system is not explained.

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 only 43% (filter, orderBy, companyName have descriptions). The description adds no parameter-level information, leaving undocumented parameters like 'top', 'page', 'skip', 'pageSize' without context. With low schema coverage, the description should compensate but does not.

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 without dormant records' uses a specific verb ('Lists') and resource ('customers') with a clear modifier ('without dormant'), distinguishing it from the sibling 'brc_list_customers' which likely includes all customers.

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 explicit guidance on when to use this tool versus alternatives like 'brc_list_customers'. The description does not mention prerequisites, exclusions, or context for selecting this tool.

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