firestarter_sync_shopify

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description adds critical behavioral context: 'Syncing runs in the background and returns immediately' and 'never changes the seller's Shopify store.' This discloses async behavior and side-effect scope, going well beyond what annotations provide, and contradicts nothing.

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?

Although lengthy, every sentence earns its place: purpose, usage triggers, prerequisites, async behavior, side effects, and parameter guidance. The description is front-loaded with the core purpose, then logically flows to usage and caveats. No fluff or 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?

The tool has one optional parameter, no output schema, and moderate complexity. The description covers all necessary context: what it does, when to use, prerequisites, background execution, non-destructive nature, and how to confirm results. It is fully complete for an agent to invoke 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?

The single parameter is fully described in the schema (100% coverage), including optionality and disambiguation purpose. The description reinforces this by saying 'pass connection_id to target a specific connection' and clarifies the default ('sync the seller's connected Shopify store'), adding slight narrative value beyond the schema's technical 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 opens with a specific verb and resource: 'Re-sync a connected store's catalog into Firestarter' and clearly states what it pulls (products, prices, inventory) and the outcome. It also distinguishes itself from related tools like firestarter_connect_shopify (connection) and firestarter_listings (verification), making its 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?

Provides explicit when-to-use guidance: 'AFTER firestarter_connect_shopify', when the seller mentions product changes, stale prices, previous sync errors, or missing items. It also states prerequisites ('store must already be connected') and what to do if not, plus a specific next step ('confirm results with firestarter_listings'). This is exemplary usage guidance.

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