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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds meaningful behavior beyond that: a per-page cap ('Pages hold up to 100 customers') and an authentication prerequisite ('Needs the user's Cotlet API key with access to this app'), which an agent needs before calling.

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 sentences are short and mostly front-loaded: purpose, scope, usage pointer, pagination limit, auth requirement. The opening fragment 'Bokio: Customers with name, type...' is slightly listy and repeats the title prefix, but nothing is redundant or padded.

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?

With no output schema, the description usefully enumerates the returned fields (name, type, organisation number, payment terms) and covers pagination and auth. For a simple 3-param read tool, that is close to complete; only an explicit 'how to fetch a single customer' note is missing.

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 100%, so the schema already documents page, search, and page_size. The description restates the search-by-name-or-email capability but adds no new syntax or constraints beyond the schema, so the baseline of 3 applies.

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 states a specific verb and resource ('Lists the customers of the company') plus the searchable dimensions (name or email) and the fields returned. It is clearly a list/read tool, but it does not explicitly differentiate itself from siblings like bokio_create_customer or bokio_list_invoices.

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?

It gives one concrete downstream use case ('Use customer_id from each item in create_invoice'), which implies why an agent would call it. However, there is no explicit when-to-use/when-not guidance and no mention of alternatives for looking up a single customer.

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