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

Goes well beyond the annotations by disclosing side effects an agent cannot predict: the shop's own automations run, customer email/SMS may be sent, webhooks may fire, dunning is exited, and Awtomic pauses on its side even if Shopify rejects the request. That last point is a critical partial-success warning not available from destructiveHint/idempotentHint.

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?

Four short sentences, front-loaded with the write operation and its effect, followed by state transition, side effects, and failure semantics — no filler. The endpoint is placed last as a reference rather than a preamble.

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 two-parameter mutation with no output schema, the description covers the state change, the inverse operation, external side effects, webhook/notification behavior, and the Shopify-rejection edge case. An agent has everything needed to call it and to warn the user about consequences.

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% and both parameters already document accepted Shopify numeric and gid forms, so the description need only anchor them via the POST path template. It adds no format or validation detail beyond the schema, making baseline 3 correct.

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?

Opens with an explicit verb+resource ('pause a subscription') and immediately states the operational effect ('not billed or shipped until reactivated'). It names the sibling that reverses it (awtomic_reactivate_subscription) and even the HTTP route, so it is unmistakable against cancel/skip/update_frequency siblings.

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?

Gives clear context for use (stop billing/shipping; move a dunning subscription out of dunning) and points to awtomic_reactivate_subscription as the inverse. It does not explicitly exclude alternatives such as awtomic_cancel_customer_subscription or skip_next_order, so the when-not case is left to inference.

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