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 adds one real behavioral fact — "Returns one page" — signaling paginated results, plus a redundant endpoint reference. It omits defaults, maximum page size behavior, and whether a total count is returned, so it adds some value but not rich context.

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 short sentences, front-loaded with the useful search semantics, with no filler. The trailing "GET /customers." is redundant implementation detail that doesn't earn its place, but it costs little.

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?

There is no output schema, so the description should describe the return shape, and "Returns one page" is the only hint — no mention of what a customer record contains or how paging terminates. For a four-parameter list tool with a documented safe-read annotation set, this is minimally adequate but leaves real gaps.

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 0%, so the description carries the full burden and only partially discharges it: "keyword or referral source" maps to keyword and referredby, but page and pagesize are never mentioned or constrained (pagesize maxes at 100). Half the parameters remain undocumented in both schema and description.

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 names a specific verb and resource ("Search customer records") and states the filterable dimensions (keyword, referral source), which distinguishes it from the singular repairdesk_get_customer. It stops short of explicitly naming the sibling it is not, so 4 rather than 5.

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 implied by the two filter dimensions it names, which tells an agent this is a browsing/search entry point. There is no explicit statement of when to prefer it over repairdesk_get_customer (single-record lookup) or the other list_* tools, and no exclusions.

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