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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds real behavioral detail on top: fuzzy/partial matching semantics, a hard 100-hit ceiling, and that results carry a relevance score. It does not describe paging behavior or what ordering to expect.

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?

One front-loaded sentence that carries the verb, scope, searched fields, result cap and ranking in a compact form. The trailing 'GET /api/v2/customers/{account}/search' is redundant API trivia that adds nothing for an agent already holding the 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 no output schema, the description carries the return-shape burden and does so adequately by noting a relevance score and a 100-hit maximum. For a three-parameter read-only search that is enough to call correctly, though pagination expectations remain unstated.

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 baseline is 3; the description earns above that by naming the fields actually searched (name, email, description), which the schema's generic 'Search text' does not reveal. The 100-hit cap also corroborates the limit parameter's maximum, though offset/paging is left entirely to the schema.

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 and resource ('Fuzzy search customers') plus the searched fields (name, email, description), which plainly separates it from the sibling tillhub_list_customers. It stops short of explicitly naming that sibling or stating that it enumerates rather than text-matches.

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?

Usage is only implied: the word 'fuzzy' signals to reach for this when text is partial, and the 100-hit cap hints at exploratory queries. The description never says when to prefer tillhub_list_customers or tillhub_get_customer, nor does it state prerequisites or exclusions.

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