ga_send_add_to_cart

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

The description says this is an ecommerce tracking event, which aligns with the annotations (readOnlyHint=false, since it sends data). It adds some context by clarifying the event is for tracking, but does not disclose additional behavioral traits such as delivery semantics, idempotency, or how the event maps to Analytics.

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?

Two short, front-loaded sentences convey the core purpose and use case without any filler. 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?

For a simple event-sending tool with a detailed input schema, the description captures the essential context. It lacks mention of response behavior or caveats about the openWorldHint annotation, but these are minor for this tool's simplicity.

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 adds no parameter-specific explanations. The input schema covers descriptions for currency, value, items, and user_properties, but leaves client_id and user_id undocumented. With 67% schema coverage, the description should compensate for the missing parameter semantics but does not.

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 opens with a specific verb and resource: 'Send an add to cart event to Google Analytics.' It clearly identifies the tool's purpose and differentiates it from sibling ecommerce events like ga_send_purchase and ga_send_begin_checkout.

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 second sentence, 'Ecommerce event for tracking when items are added to shopping cart,' clearly states the trigger condition for using this tool. It does not explicitly exclude alternatives, but gives enough context for when this event is appropriate.

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