firestarter_connect_store

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

The description implies a write operation (connecting a store) and describes a two-step flow: checking for existing connections and then providing credentials. While it doesn't explicitly state side effects like creating or updating a connection, the term 'connect' conveys the primary behavior, and the annotations (readOnlyHint=false) already signal a non-read-only operation.

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 compact and free of redundant information. Each sentence serves a purpose: listing supported platforms, pointing out alternative tools, and outlining the two-step calling convention. No unnecessary verbosity.

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?

The description is self-contained: it identifies supported platforms, differentiates from sibling tools, and explains the invocation pattern. It covers the essential steps and parameter usage without requiring additional context. The lack of an output schema is acceptable since the tool's primary purpose (connecting) and its two-phase flow are clearly communicated.

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 already describes four of five parameters (shop_domain, access_token, consumer_key, consumer_secret) with meaningful details. The description adds context for the `platform` parameter by explaining that it can be used alone initially to retrieve credential instructions or check existing connections, filling a gap in the schema's own description.

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 (connect a store) and specifies the supported platforms (BigCommerce, Shopee, Lazada, Wix, WooCommerce). It also explicitly excludes Shopify and TikTok, directing users to dedicated tools, making the purpose unambiguous.

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 provides explicit instructions on when to call with only the platform (to check for existing connections or get credential instructions) versus when to call with full credentials. It also references sibling tools for Shopify and TikTok, ensuring correct tool selection.

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