publish-product

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

With no annotations, the description carries the full behavioral burden. It discloses that the tool returns the product's channel states and userErrors, which is valuable, but it does not mention permissions, whether it adds to or replaces existing publications, or idempotency on repeat calls, which matter for a mutation.

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 that covers purpose, targeting options, the reference tool, and return values without waste. Every clause 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 mutation tool with no annotations and no output schema, the description supplies the important pieces: how to target channels, where to obtain IDs, and what comes back (channel states and userErrors). Minor gaps remain around preconditions and side effects on already-published channels.

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 coverage is 100%, so parameter meaning is already fully documented, including the either/or requirement for publicationIds vs publicationNames. The description reinforces 'exact' names and cites get-publications as the source, but adds little else 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?

States a specific verb and resource (publish a product) plus the scope (one or more sales channels), and points the agent to get-publications for channel identifiers. It is clearly distinguishable from the sibling unpublish-product and from channel management 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?

Explains the two ways to target channels (publicationIds or exact publicationNames) and tells the agent to consult get-publications for the values. It does not explicitly say when to choose this over unpublish-product or when publication is not appropriate, but the context for use is clear.

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