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

Annotations already establish the safe read-only profile. The description adds useful behavioral context beyond annotations: every client is returned at once, the tool filters and pages internally, each row carries counts, and include_details yields large payloads. It does not cover auth or rate limits, but that is a minor gap against the annotation baseline.

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 front-loaded, uses three tight sentences, and every element (returned fields, include_details behavior, internal paging) earns its place. The endpoint suffix is a small addition but not wasteful.

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 read-only list tool with full schema coverage and no output schema, the description sufficiently explains the return shape and paging. The one missing piece is guidance on when to use this versus the dedicated list_client_addresses or list_client_contacts siblings, which an agent might reasonably consider.

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 all five parameters are fully documented in the input schema. The description reinforces include_details and notes the internal paging behavior, but adds little beyond what the schema already explains for limit, offset, search, and active_only. Baseline 3 is appropriate.

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 ('clients') and enumerates the fields returned, so an agent can tell it is a list operation distinct from get_client. However, it does not explicitly name or contrast with the closest siblings (get_client, list_client_addresses, list_client_contacts), leaving some differentiation implicit.

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 when to use the tool (to retrieve all clients) and explains that filtering/paging happen inside the tool, but it never explicitly says when to prefer get_client or the dedicated address/contact list tools over this one. Parameter-level guidance for include_details is present, but tool-selection guidance is only implied.

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