cart_add_promotions

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

With no annotations, the description carries the full burden of behavioral disclosure. 'Generate' implies creating code or files, but the description does not mention side effects, project modifications, authentication needs, or whether anything is overwritten.

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 a single, front-loaded sentence with no filler, and 'Pro feature' is a useful qualifier. It is concise though very sparse, sacrificing substance for brevity.

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 tool with no annotations, no output schema, and incomplete parameter descriptions, this is too thin. It lacks the prerequisites, usage context, and behavioral details an agent needs to invoke it correctly.

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 schema only describes 'directory' and leaves 'api_key' undocumented. The description adds no parameter-level meaning and does not explain how api_key or directory are used, despite the 'Pro feature' hint implying licensing may matter.

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 action ('Generate') and resource ('cart promotion engine'), and adds the 'Pro feature' qualifier. However, it does not explicitly differentiate itself from sibling tools like cart_generate_system or cart_add_persistence beyond naming the promotion engine.

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?

There is no guidance on when to use this tool versus alternatives. It does not state whether a cart system must already exist, whether this is an add-on to cart_generate_system, or what conditions make it the right choice.

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