Search Shopify Customers

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the query-filter syntax, which is genuine value, but says nothing about pagination behavior or result ordering beyond what the annotations and schema provide.

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?

Two sentences, front-loaded with the core capability and followed by high-value examples. No filler; every element earns its place.

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 readOnly/idempotent annotations covering safety and no output schema to explain, the description only needs to convey search semantics, which it does via the filter examples. It is slightly thin on pagination ('after'/'limit') expectations, but that is documented in the schema.

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 67% (query and after described, limit undocumented). The description compensates by demonstrating concrete query syntax strings ('email:bob@example.com', 'tag:vip', 'state:enabled'), which adds real meaning beyond the schema's bare 'Search query' label.

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 (search customers) and enumerates the searchable fields (name, email, tags, or any customer query filter). It clearly separates this from get_customer by framing it as a search, though it does not explicitly name the sibling tools it competes with (shopify_get_customer, shopify_search).

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 query examples showing filter syntax, but there is no explicit guidance on when to use this versus shopify_get_customer (single lookup) or the generic shopify_search. No prerequisites or exclusions are stated.

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