shopify_publish_resource

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

The annotations already signal mutation (readOnlyHint=false) and destructive potential (destructiveHint=true), but the description adds no behavioral context such as irreversible visibility changes, permission requirements, or the effect of publishing on existing sales channels. It does not contradict the annotations, but it also does not disclose anything beyond the bare action.

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, front-loaded sentence with no filler: subject, action, resource, and target are all present. 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 destructive, non-idempotent mutation with four required parameters and no output schema, the description is too thin. It omits the confirm/authorization requirement, how to obtain valid publicationIds, and any guidance on when publishing is appropriate, so a new agent would need to infer too much.

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 only 25% (only confirm is documented), so the description must compensate for the other parameters. It clarifies 'id' as product/collection and hints that publicationIds are the targets, but it does not cover 'store' or the confirmation gate beyond what the schema already states.

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 names a specific verb ('Publish'), the resources ('a product or collection'), and the target ('explicit publication IDs'), so an agent can identify what the tool does. It does not explicitly contrast it with siblings such as shopify_create_product or shopify_bulk_update_product_status, but the wording is specific enough to avoid confusion.

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 about when to choose this tool over alternatives like shopify_list_publications or shopify_graphql_mutation, and no exclusions or prerequisites. The only hint is 'explicit publication IDs', which implies the caller must already know the target publication IDs, but this is not developed.

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