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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description contributes the return-field set and the underlying endpoint, which is useful context, but says nothing about pagination behavior, result caps, or permission requirements beyond what the schema states.

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?

Three tight sentences, front-loaded with the action and filters before the return payload and endpoint. Nothing is padding, though the trailing 'GET /customer/list' is of marginal value to an agent choosing a tool.

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 8 optional parameters, no required inputs, a rich 88% schema and full annotation coverage, the description is nearly sufficient, and it helpfully compensates for the absent output schema by naming the returned fields. The remaining gap is sibling differentiation from get_customer and create_customer.

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 88%, so parameters (wildcard name, exact e-mail, active flag, changed_since, paging) are already well documented in the schema. The description only restates a subset of these filters ('name wildcard, e-mail, active flag, change time') without adding syntax, defaults, or edge-case behavior. Baseline 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?

States a specific verb ('list or search') and resource ('customers'), enumerates the filterable dimensions, names the return fields, and even cites the backing endpoint GET /customer/list. It stops short of distinguishing itself from the sibling synchroteam_get_customer, so an agent still has to infer that this is the bulk/collection variant.

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 phrase 'list or search' plus the parenthetical filter list implies when filtering is appropriate, but there is no explicit when-to-use statement, no prerequisites, and no pointer to the single-record alternative synchroteam_get_customer. Usage must be inferred rather than read.

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