get_ecommerce_product_activity

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

Comprehensive disclosure despite no annotations: read-only, safe to retry, authentication via API key, max 10 concurrent requests, error scenarios, and behavior when integration not active.

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?

Well-structured: purpose first, then requirements, error handling, parameters, return format. Each sentence is informative; no fluff.

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?

Covers all essential aspects: prerequisites, input parameters, return format, errors, rate limits, and mentions related tool for verification. Sufficient for an AI agent to use 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?

All three parameters are explained in detail despite 0% schema coverage: campaign_id with example and constraint, count with range and default, offset with usage guidance. Adds significant value beyond schema.

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?

Description clearly states 'Retrieve e-commerce product activity for a campaign showing revenue per product.' Verb and resource are specific, and it distinguishes from siblings (e.g., list_ecommerce_stores).

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?

Explicitly mentions prerequisite (active integration), fallback behavior (total_items=0 if none), verification via list_ecommerce_stores, and scope (only for sent campaigns). Also covers error handling (404) and rate limits.

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