firestarter_import

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

Annotations only say readOnlyHint=false and destructiveHint=false; the description adds crucial behavioral details: the result is a non-live, non-buyable draft with no share link, a fetch is still attempted even for blocking platforms, and activation depends on price and photo. No contradiction with annotations.

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 long but each sentence carries necessary operational information: purpose, platform caveats, failure handling, and activation prerequisites. It is front-loaded with the core purpose and follows a logical flow without redundant filler.

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?

Given no output schema and sparse annotations, the description thoroughly covers input modes, blocked-platform behavior, error codes, recovery steps, and downstream activation requirements. The draft outcome is clear, making the tool effectively self-contained for an agent.

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?

Although schema coverage is 100% with good per-parameter descriptions, the main description adds cross-parameter strategy (send source_url AND raw_text together for blocked platforms) and the role of photos/price for activation. This goes well beyond the schema's individual property docs.

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?

Opens with a specific action ('Import') and resource ('a seller's EXISTING listing from another marketplace'), and immediately states the output is a DRAFT listing for review. This clearly distinguishes it from sibling listing tools like firestarter_list or firestarter_bulk_list.

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 platform-specific strategy: send source_url with raw_text and photo_urls up front for known bot-blocking sites, and how to recover from PLATFORM_BLOCKED/EXTRACTION_EMPTY by asking the seller for pasted text. It also names firestarter_update_listing and firestarter_reprice for activation, giving clear next-step context.

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