firestarter_register_seller

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses idempotency ('returns the existing profile without error'), error-recovery protocol (NO_SELLER_PROFILE), and post-registration behavior (immediate listing, payouts later). This gives the agent a robust understanding of the tool's behavior.

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 every sentence carries actionable information: purpose, prerequisite, error handling, idempotency, and follow-up. It is front-loaded with the core purpose and has no filler, though it could be marginally tighter by merging related clauses.

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?

For a simple two-parameter registration tool with no output schema, the description fully covers prerequisites, error scenarios, idempotency, and post-conditions. Nothing important is missing, and the agent has enough context to use it correctly in any workflow.

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 for both parameters, including descriptions and an enum for type. The description adds the key clarification 'Only requires a business_name' and reinforces that payouts are not needed upfront. This modest add-on elevates it slightly above the baseline 3.

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 clear verb+resource statement: 'Register the current account as a seller on Firestarter.' It distinguishes itself from sibling tools by explicitly naming dependent tools (firestarter_list, firestarter_import, firestarter_connect_shopify) that require this registration first.

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: required before listing, importing, or connecting a store, and specifically instructs to call this first if NO_SELLER_PROFILE is returned, then retry the original tool. Also clarifies that payouts can be set up later, preventing the agent from over-requiring setup steps.

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