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

The readOnlyHint=true annotation already establishes this is a safe read, so the description's 'Bookeo: GET /customers' mainly confirms it. It adds the optional-filter semantics but says nothing about pagination flow, default page size, or result ordering beyond what the schema already declares.

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?

A single dense sentence front-loads the core action and folds filters and the underlying endpoint into one pass with no filler. Nothing in it is redundant padding.

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 an eight-parameter listing tool with no output schema, the coverage is solid: the description signals the searchable fields and the member/date filters, and the schema handles pagination tokens and defaults. Only the shape of the returned customer list and pagination expectations are left implicit.

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 all eight parameters (pageNumber, searchText, searchField, createdSince, itemsPerPage, currentMembers, currentNonMembers, pageNavigationToken) are already documented in the schema. The description restates the search fields and member filters without adding format, default, or interaction details.

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?

States a specific verb (list/search) and resource (customers) and enumerates the filter dimensions, so an agent can tell it apart from bookeo_get_customer or bookeo_create_customer. It stops short of naming the sibling list/get tools explicitly, but the scope is unambiguous.

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 usage ('search ... by name, firstName, lastName or emailAddress ... optionally only members/non-members or created since a date') but never states when to prefer it over bookeo_get_customer for a single customer or bookeo_list_customer_bookings. No exclusions or prerequisites are given, so the routing is left to inference.

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