firestarter_connect_tiktok

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

Goes well beyond the minimal annotations by disclosing idempotent behavior ('If a TikTok Shop is already connected, returns its status'), the current auth method (access token, not OAuth), and a critical security warning about never displaying the token. This adds meaningful context about how the tool behaves in practice.

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 six sentences long but remains focused and front-loaded with the primary purpose. Each sentence adds essential information, from the core action to auth details to call patterns and a security warning. It could be slightly tightened, but there is no 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?

Covers the two primary use cases (status/instructions vs. creation) and provides security context. It mentions the status return when already connected, but does not explicitly describe the return value for successful creation or error cases. Given no output schema, this is a minor gap, so 4 is appropriate.

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 schema already provides 100% coverage of both parameters, so the baseline is 3. The description adds value by clarifying the conditional relationship (omit access_token for status, include it with shop_domain for creation) and emphasizing the secret nature of the token. These extras justify a 4.

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 tool's function: connecting a seller's TikTok Shop to Firestarter for catalog sync and order flow. It explicitly names TikTok Shop, distinguishing it from sibling tools like connect_shopify and connect_store. The dual purpose (create connection or return status) is also clearly identified.

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?

Provides strong usage guidance: 'Use this whenever a seller mentions TikTok Shop or wants to sync their TikTok products.' It also specifies two invocation modes (no arguments for status/instructions, or with access_token and shop_domain for creation) and explains the prerequisite of obtaining an access token from TikTok Partner Center. This is explicit and actionable.

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