shopify_delete_webhook_subscription

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

Annotations already carry destructiveHint=true and idempotentHint=true, so the description does not need to restate those. It adds useful governance context around effect verification, approval_ref, and project/connector auth fields, but does not describe deletion consequences, failure behavior, or idempotency semantics. Acceptable but not rich.

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?

One-sentence purpose followed by a compact, aligned Args block with no filler and no repetition of schema type information. The action is front-loaded and every line 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 7-param destructive tool with annotations and an output schema, the description covers the core behavior and all parameter semantics, so the agent can construct a valid call. It lacks explicit usage alternatives and some behavioral detail, but annotations and output schema carry much of that weight.

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?

With 0% schema description coverage, the Args section compensates by giving each of the 7 parameters at least a one-line semantic meaning, including numeric/GID format for webhook_subscription_id and the role of approval_ref. Some descriptions are terse or slightly ambiguous, and webhook_subscription_id is marked required in prose while the schema leaves it nullable, but overall the description adds substantial meaning beyond the schema.

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 the exact operation: delete a Shopify webhook subscription by ID, and identifies the key parameter as numeric or GID. Among many shopify_* delete tools, it explicitly names the resource (webhook subscription), so sibling confusion is unlikely.

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?

No guidance about when to choose this over shopify_create_webhook_subscription or shopify_list_webhook_subscriptions, and no mention of prerequisites such as looking up the subscription ID first. The 'Delete...' sentence restates purpose rather than providing decision context.

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