shopify_shop

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

No annotations are provided, so the description carries the entire behavioral burden, yet it says nothing about read-only behavior, authentication requirements, or error conditions. The parameter names (api_key, access_token) hint at auth, but the description never confirms that callers must supply valid credentials or what happens when they don't.

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?

A single short sentence with no filler, but it is under-specified rather than concise; there is no front-loaded detail an agent can act on beyond the bare purpose.

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?

A three-parameter authenticated API tool with no annotations, no output schema, and no parameter documentation gets almost nothing from this description. An agent would know what the tool is for but not how to invoke it correctly or what it returns.

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 needs to compensate for three undocumented parameters and does not. The names api_key, shop_domain, and access_token are largely self-explanatory (domain format, where to obtain keys), which keeps this above a 1, but the description adds zero meaning.

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 ('Get Shopify store information'), distinguishing it from the transactional siblings like shopify_orders and shopify_products. It does not state what 'store information' actually comprises (name, currency, plan, domains), leaving scope somewhat open.

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?

There is no guidance on when to call this versus the other shopify_* tools, no prerequisites, and no mention of what to do if credentials are missing. The agent must infer that this is the account/store-metadata entry point.

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