Find Shopify Admin Actions

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds useful behavior beyond that: the seven return fields (including a destructive flag and which dedicated tools already cover each action) and the discovery-then-execute workflow.

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 sentences, front-loaded with purpose, then return payload, then next steps. No filler and nothing repeated from the schema.

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?

No output schema exists, and the description covers the return shape and the follow-on tool chain, which is what an agent needs to act. It omits pagination behavior (limit/offset, the 50-cap) and default store/apiVersion resolution, leaving a minor gap for a discovery tool.

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 only 43% across 7 params, but the description does explain the two most consequential ones - keyword search (query) and optional category. limit, offset, includeDeprecated and the apiVersion interplay remain undocumented anywhere, so it only partially compensates for the coverage gap.

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+resource+scope: search every Shopify Admin API mutation, including the hundreds of write actions that lack a dedicated tool. This cleanly distinguishes it from sibling search/describe/run tools and from the dedicated mutation tools listed.

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?

Explicitly tells the agent what to do next (shopify_describe_action for the signature, then shopify_run_action), which is strong routing guidance. It doesn't state a when-not or contrast against shopify_search / shopify_graphql_schema, so not a full 5.

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