brc_list_customers_without_dormant

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

No annotations provided, so description bears full burden. It only states the basic function without disclosing behavioral traits such as pagination, sorting, performance implications, or the exact meaning of 'without dormant'. Lacks detail for a list tool with multiple parameters.

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?

Single sentence is concise and front-loaded. However, given the tool's complexity (7 parameters, no annotations), it may be underspecified. Nevertheless, it avoids verbosity.

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?

Despite the complexity (7 params, no output schema, no annotations), the description offers minimal context. It omits return format, pagination behavior, and a precise definition of 'without dormant'. Incomplete for effective use.

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 only 43% (3 of 7 parameters have descriptions). The description does not add any meaning beyond the schema; it fails to explain parameters like top, page, skip, pageSize, or how they interact. With low coverage, 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?

Description clearly states verb 'Lists' and resource 'BRC customers' with a specific filter 'without dormant records'. This distinguishes it from similar siblings like brc_list_customers, which likely lists 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 guidance on when to use this tool versus alternatives, no exclusions or prerequisites mentioned. The description provides no context for selecting this tool over brc_list_customers or others.

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