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

Annotations already cover the safety profile (readOnlyHint=true), yet the description adds real behavioral context: a 30-per-page pagination size, the fact that every filter is an exact match, and the response-size benefit of `only`. It stops short of stating total-count behavior or the 10,000-page cap, so it is not exhaustive, but it meaningfully exceeds the annotations.

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?

Four tight sentences, front-loaded with the core purpose and pagination fact before the tips. Every sentence carries signal; only the trailing endpoint reference ('GET /{account}/customers.xml') is mildly redundant for an agent, preventing a 5.

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 and 12 optional params, the description supplies the essentials an agent needs: collection intent, page size, exact-match filtering, and a response-slimming lever. Acceptable embedding details like `include` are left to the schema, which is reasonable given its full coverage.

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 baseline is 3, but the description goes slightly beyond the per-field docs by generalizing 'Every filter is an exact match on that field' across all 12 params and explaining the payoff of `only`. This reinforces semantics the individual schema blurbs state piecemeal.

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 opens with a specific verb+resource, 'List or search customers', which clearly indicates a collection read vs. a single-record read. However, it never names the distinguishing sibling (kickserv_get_customer for a single lookup), so the differentiation from siblings is only implied by the plural noun.

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 offers one concrete usage tip ('Use `only` to keep the response small') and states that filters are exact matches, which is operationally useful. But it never says when to reach for this tool instead of kickserv_get_customer or kickserv_list_customer_jobs, and gives no exclusions or prerequisites, leaving most routing to inference.

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