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

The annotations already disclose readOnlyHint=false, destructiveHint=true, and openWorldHint=false. The description adds only that publishing is separate; it omits what the destructive edit changes, how expected_revision conflicts behave, and why idempotency_key and the 25-op batch limit matter.

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 core action is front-loaded, but the description is under-specified rather than efficiently concise. The 'guides_get commerce/api draft/<type>' fragment is cryptic and does not compensate for the missing operational detail.

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?

This is a destructive, batch-oriented mutation with six parameters, a nested ops enum, no output schema, and no schema descriptions. The definition leaves nearly all operational requirements undocumented, so it is not complete enough for safe invocation.

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 0% for six parameters, and the description does not explain ops, build_id, expected_revision, idempotency_key, workspace, or take_over. The fragment 'draft/<type>' does not document the nested operation types either.

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 states a specific verb and resource: 'Edit commerce drafts,' and 'Publish separately' scopes it away from publishing/live operations. It does not name the relevant sibling publish/live tools or clarify draft types, so it falls short of a 5.

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 only usage cue is 'Publish separately' plus an opaque docs pointer. It does not say when to use this rather than commerce_draft_get or commerce_live_apply, nor does it state prerequisites such as revision or idempotency requirements.

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