List Shopify Stores

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description need not repeat safety traits. It adds the valuable behavioral note 'does not expose access tokens,' which is a security guarantee beyond the annotations, and 'remains connected' implies filtering of disconnected stores, adding context about what 'list' means.

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?

The description is two sentences with no filler. It front-loads the main action and scope, then adds a single important security clarification. Every word 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?

For a zero-parameter, read-only list tool, the description is sufficient. It covers the core operation and a key security aspect, though it does not specify what the return list contains (e.g., store names, IDs). Since there is no output schema, this minor gap is acceptable given the tool's simplicity and the annotations covering safety.

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?

The input schema has zero parameters, so there are no semantics to describe. The description does not need to compensate for missing parameter docs, and the baseline for zero-parameter tools is 4.

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 ('List'), resource ('Shopify Admin store'), and scope ('remains connected to this plugin'), clearly distinguishing this from sibling tools like shopify_get_shop_info or shopify_graphql_query. It is unambiguous about what the tool does.

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?

The description implies usage: an agent would use this to enumerate connected Shopify stores. However, it does not explicitly compare to alternatives or state when not to use it, such as 'use shopify_get_shop_info for a single store's details.' The context signals are sufficient for inference but not explicitly provided.

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