cigchat_subscriber_add_to_cart

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

No annotations are provided, so the description bears the full burden. It discloses the authentication scope ('Manage Flow') but does not explain what happens on success, whether the operation is idempotent, or what response to expect. It also doesn't clarify if this appends or replaces cart items.

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 description is extremely concise and front-loaded with the key verb and resource. No filler words; every phrase 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?

The tool is a mutation with no annotations, no output schema, and weakly described parameters. The description omits critical context such as the response format, error behavior, or how this relates to other cart tools like remove_from_cart. It's minimally viable but incomplete.

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?

The description doesn't explain any parameters. The schema provides only example values for qty and variant_id, and user_ns has no description, leaving the required identifier ambiguous. With 67% coverage but no semantic meaning, the description fails to clarify what these fields represent.

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 ('Add') and resource ('item to subscriber shopping cart'), and includes the endpoint. This clearly distinguishes it from sibling tools like remove_from_cart and empty_cart.

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 description provides no explicit guidance on when to use this tool versus alternatives such as remove_from_cart or cart. The only contextual information is the required 'Manage Flow' scope, which is a prerequisite, not a usage guideline.

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