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

Annotations already declare WRITE semantics (readOnlyHint=false), openWorldHint, idempotentHint and destructiveHint, so the 'WRITE:' prefix is largely redundant. The description does add genuine behavior: the operation is additive and preserves existing links. It does not explain why an append would be flagged destructive, nor what happens on duplicates or the 500-item cap.

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?

A single lean sentence with the operation type front-loaded, zero padding. The trailing HTTP endpoint is mildly redundant with the tool name and schema but not harmful.

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?

With only two required params, 100% schema coverage and rich annotations, the description covers the essentials. Remaining gaps are duplicate-handling and the 1-500 array bound, which the schema partially covers via minItems/maxItems.

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 100%, with rule_id, product_id and variant_id each documented in-schema (including 'null for all variants'). The description adds no meaning beyond restating 'products or variants', so the baseline 3 applies.

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 a specific verb and resource ('Add products or variants to a subscription rule') and adds scope: appending without touching already-linked items. That implicitly separates it from replace-style edits, though it never names the sibling (e.g. sealsubscriptions_edit_subscription_rule) it contrasts with.

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 phrase 'without touching the ones already linked' implies when to choose this over a full edit, but no alternative is named and no preconditions (rule must exist, products must belong to the shop) are given. Usage must be inferred.

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