发布商品

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

Annotations already indicate the operation is not read-only, but the description adds meaningful behavioral context by stating that store visibility changes and that user confirmation should be obtained before calling. This goes beyond the annotation metadata and helps the agent understand side effects.

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 short sentences with no redundancy. The core purpose is front-loaded, followed by the key behavioral caveat and confirmation requirement. Every sentence 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 moderate-complexity mutation with no output schema, the description plus schema and annotations is sufficient for correct invocation: it states the product prerequisite (ACTIVE), the target (sales channels), the effect (visibility change), and the need for confirmation. Minor omissions like return values or error behavior are not critical for selecting and calling this tool.

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 33%, covering publishAt. The description partially compensates by indicating that id must refer to an ACTIVE product and that publicationIds are the target sales channels, but it does not provide detailed parameter-level semantics beyond what the schema already offers.

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 clearly states the action: publishing ACTIVE products to specified sales channels. This specific verb+resource combination distinguishes it from sibling tools like shopify_unpublish_product or shopify_set_product_status, even without naming them.

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 when to use the tool—when an ACTIVE product should be made visible on a sales channel—and includes a confirmation requirement. However, it does not explicitly mention alternatives or state when not to use it versus other siblings.

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