shopify_list_publications

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, covering the safety profile. The description adds prerequisite context but does not disclose return shape, pagination, or other behavioral details; with these annotations, this is acceptable but not rich.

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 that front-loads the verb and resource and immediately states the relevant usage context. Every word is purposeful, with no redundant filler.

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 simple one-parameter read-only tool, the description gives the core purpose and timing. However, with no output schema and no explanation of the store parameter or response structure, there is some ambiguity left for the agent. Annotations cover safety, but the description alone is only moderately complete.

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%, and the description does not mention the store parameter at all. It adds no meaning beyond the schema's name, type, and length constraints. Since the description must compensate for low schema coverage, this is a notable gap, even though the single parameter is relatively self-explanatory.

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') and resource ('publication IDs'), and clarifies the operational purpose by saying 'before publishing products or collections.' This clearly distinguishes it from publishing, search, and other sibling tools.

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 explicitly communicates when to use this tool: before publishing products or collections. It does not name alternatives or exclusions, but the timing context is clear enough for an agent to select it as a prerequisite step.

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