Create Shopify Article

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

Annotations already declare a non-readonly, non-idempotent, non-destructive open-world write, so the safety profile is covered structurally. The description adds nothing beyond that: it does not say whether a duplicate call creates a second article, what the default publish state is, or what happens on missing blogId — all meaningful for a create tool.

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 tight sentence with the action front-loaded and no filler. It is efficient, though its brevity is also the source of the content gaps elsewhere.

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 7-parameter mutation with a nested author object, no output schema, and only 43% schema coverage, the description leaves too much unstated — required blogId, the nested author.name shape, and the published default are all left to the schema or guesswork.

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 43% (below 50%), so the description is expected to compensate, but it only echoes body/author/summary/tags. It omits blogId (required, the most error-prone parameter), title (required), and published, leaving the required-vs-optional split and the blog scoping unexplained.

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 ("Create a new blog article") and enumerates the main content fields, so an agent can distinguish it from shopify_update_article and the other create_* tools without opening a schema. It stops short of explicitly naming the update/read siblings it is not.

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 use this versus shopify_update_article, no mention that an existing blog (blogId) must already exist, and no note about draft-vs-published workflow. The agent must infer all invocation context.

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