list_ecommerce_stores

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

Annotations already provide readOnlyHint=true and destructiveHint=false, so the description adds minimal behavioral detail beyond mentioning its role in verifying integration and returning empty if no integration. No side effects or auth needs 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?

The description is relatively concise, with the purpose front-loaded and usage guidance separated. The return format is included, but every sentence serves a purpose. Slightly verbose due to repeated returns format in both description and output schema.

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?

Despite having an output schema, the description includes the return format and usage guidance. However, it fails to cover the 'account' parameter, leaving the tool incompletely documented for a simple single-parameter tool.

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 input schema has one optional parameter 'account' with 0% description coverage. The description does not explain the meaning of 'account' at all, leaving the agent to guess its purpose. This is a significant gap.

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 it lists connected e-commerce stores with platform and currency info, specifying types like Shopify and WooCommerce. It distinguishes from sibling tools by explaining its role in discovering store IDs for other list tools.

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 description explicitly says to use it for discovering store IDs for list_store_orders, list_store_products, and list_store_customers, and for verifying integration status before get_ecommerce_product_activity. This provides clear context, though it lacks explicit exclusion of alternatives.

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