List customers

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

With no annotations, the description carries the full burden. It adds behavioral details by explaining that `search` performs a name substring match and `filter` takes a raw OData $filter, which goes beyond the schema. However, it does not mention pagination default/limits (top/skip) or the output shape, which are left to the schema.

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 two sentences long, with the first sentence stating the purpose and the second providing parameter usage. Every sentence earns its place; no fluff or repetition.

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's simplicity and full schema coverage, the description adequately covers the core functionality and parameter behavior. It lacks explicit mention of alternative tools (e.g., bc_get_customer for a single customer) and output details, but these are not critical for a straightforward list operation.

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 100%, so the baseline is 3. The description adds 'Use `search` for a name substring match, or `filter` for a raw OData $filter,' which reinforces the schema but does not introduce new information about the parameters beyond what the schema already provides.

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 states 'List customers' with a specific verb and resource, and the phrase 'in the working company' adds useful context. It distinguishes itself from sibling tools like bc_list_items, bc_list_vendors, and bc_get_customer by focusing on the customer list resource.

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 provides guidance on using the `search` and `filter` parameters, but does not explicitly mention when to use this tool over alternatives like bc_get_customer or bc_query. The usage context is implied by the tool's name, but no exclusions or alternative tool recommendations are given.

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