List customers

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

Annotations already cover read-only, idempotent, and non-destructive behavior, so the description does not need to repeat those. It does add the behavioral notes 'paging and free-text filtering,' but it does not disclose defaults, sort order, or response details, so the added transparency is moderate.

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 one short, well-ordered sentence. It front-loads the core action ('Lists customers') and then adds the two most important modifiers. There is no wasted or redundant language.

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?

For a simple, read-only list operation with no required parameters and full schema coverage, the description is mostly complete. It could add minor context like default page size or what the response includes, but the absence is not a serious gap given the annotations and schema.

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 schema already documents page, query, and pageSize. The description adds only the high-level mapping: 'paging' to page/pageSize and 'free-text filtering' to query. This meets the baseline but does not enrich parameter understanding beyond 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 uses a specific verb and resource: 'Lists customers' with explicit capabilities ('paging and free-text filtering'). This clearly separates it from single-customer retrieval (bokio_get_customer) and from lists of other entities like bokio_list_suppliers.

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 implies the tool is for retrieving a paged, filterable collection of customers, which gives usable context. However, it does not explicitly state when to prefer this over alternatives such as bokio_get_customer, nor does it include any when-not-to-use guidance.

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