list_ecommerce_stores

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

No annotations provided, but description compensates fully: authenticates via API key, max 10 concurrent requests, read-only and safe to retry, notes total_items: 0 if no integration configured. All behavioral traits beyond basic read operation are disclosed.

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?

Front-loaded with purpose, followed by usage guidance, behavioral info, and return format. Every sentence adds necessary detail without 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?

No params to document; output schema exists but description still provides expected return structure (total_items, stores array with fields). Complete for a list tool with good context signals.

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?

Input schema has no parameters (0 params, 100% coverage), so description does not need to explain parameters. It adds value by detailing the return structure and how to use returned IDs.

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 explicitly states 'List connected e-commerce stores' with examples (Shopify, WooCommerce) and platform/currency info. It clearly differentiates from sibling tools like list_store_orders or list_store_products by focusing on 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?

Describes use cases: discover store IDs for list_store_orders, list_store_products, list_store_customers, and verify integration status before get_ecommerce_product_activity. Does not explicitly state when not to use, but context is clear.

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