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

The annotations already declare this is a non-read-only, non-destructive, non-idempotent operation. The description adds valuable behavioral context beyond them: the new item remains a draft and 'nothing changes on the store until the merchant publishes it,' and it signals a dependency on get_write_guide for field names. It does not cover permissions or failure behavior, but the core deferred-effect trait is well disclosed.

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?

Three well-structured sentences, front-loaded with the core action, followed by the key behavioral constraint and a procedural pointer. Every sentence earns its place, and the examples are brief and helpful.

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?

Given four parameters, a nested `item` object, and no output schema, the description covers the essential purpose, the draft/non-live behavior, and the get_write_guide dependency. It leaves gaps around the `kind` parameter and workflow alternatives (e.g., what to do after creating the draft), but those are minor relative to the core call requirements.

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 75%, so the baseline is 3. The description reinforces the `item` parameter's write-guide field naming, but that is already present in the schema, and it adds nothing for the undocumented `kind` parameter. It does not compensate for the remaining schema gap.

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 a specific verb and resource: creating a new item as a draft, with examples of item types. It distinguishes draft creation from direct store changes by noting that nothing changes until the merchant publishes, but it does not explicitly name sibling alternatives such as edit_draft or stage_changes.

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?

Usage context is implied: use this to prepare a new item without affecting the live store. However, there is no explicit when-to-use guidance versus siblings like edit_draft, discard_draft, or stage_changes, and no stated exclusions. The instruction to use get_write_guide field names is a procedural tip rather than an alternative-selection rule.

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