firestarter_register_seller

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the description isn't the sole source. It adds idempotency (returns existing profile without error) and the cross-tool dependency. It doesn't detail response shape or side effects beyond idempotency, but given annotations coverage, this is a solid 4.

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?

Description is longer than minimal but every sentence earns its place—precondition, idempotency, expected error, immediate usability. Front-loaded with the core purpose. Slight verbosity but justified by the context needed.

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 the tool's moderate complexity and no output schema, the description covers prerequisites, behavior, and relationships. It hints at return profile in the idempotent case but doesn't explicitly state what a successful first-time registration returns. Minor gap, but overall well-rounded.

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?

Schema descriptions cover 100% of parameters and are already rich (e.g., country's Stripe implication, type defaults). The description adds 'Only requires a business_name' which is redundant with the required field. No new semantic value beyond the schema; baseline 3 applies.

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?

Clear verb 'register', resource 'account as a seller', and explicitly names dependent tools (list, import, connect_shopify). The description states what the tool does and differentiates it from siblings by explaining it's the precondition for listing/importing. Highly specific.

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?

Explicitly states when to use (before listing/importing/connecting) and the symptom (NO_SELLER_PROFILE error) if not yet registered. Also clarifies that payouts can be deferred, so it's not needed for immediate listing. Clear guidance on when and when not to use.

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