tiendanube_add_cart_item

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. It fails to mention side effects, required authentication, cart existence prerequisites, or behavior when both cart_id and cart_token are provided. The description is too brief for a mutation tool.

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 sentence, concise and front-loaded with the tool name. It avoids unnecessary words but could be slightly restructured to remove redundancy.

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?

Given no annotations, no output schema, and 4 parameters, the description is inadequate. It does not explain return behavior, error cases, or validation rules (e.g., required cart identifier). The tool's role among many siblings is not clarified.

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 each parameter has a basic description. The tool description adds minimal value (e.g., 'by id or token' hints at cart identification but does not clarify exclusivity or precedence). Baseline of 3 is appropriate as schema does the heavy lifting.

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 clearly states the action: adding a variant to a cart by id or token. It is specific and distinguishes from siblings like 'remove_cart_item' and 'update_cart_item_quantity'. However, it does not explicitly mention alternatives or exclude other cart modifications.

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 usage guidelines are provided. The description does not indicate when to use this tool versus other cart-related siblings such as 'tiendanube_clear_cart', 'tiendanube_apply_cart_coupon', or 'tiendanube_create_draft_order'. There is no context on prerequisites or exclusions.

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