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

With no annotations, the description carries the full burden and does substantial work: it discloses that the tool registers or links an account, returns a Stripe Connect onboarding link, applies a 95% fee schedule, and has prohibited-use rules. It also explains the Stripe-vs-USDC branching behavior for unsupported countries. It does not mention side effects like API key minting or whether the operation is reversible, but the main behavioral traits are well covered.

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 information-dense, and the core purpose is front-loaded. Every sentence contributes useful guidance: payout mechanics, fee schedule, exclusions, and alternatives. It is a single dense paragraph rather than structured bullets, which slightly hurts scannability, but there is no wasted content.

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 complexity, no output schema, and no annotations, the description covers the essential call context: return value (Stripe Connect onboarding link), country handling, free-listing exception, fee schedule, prohibited items, and the health-data alternative. It does not specify the exact response shape or all error cases beyond the 400 for unsupported countries, but the information needed to invoke the tool correctly is largely present.

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 coverage is 100%, so the baseline is 3. The description adds meaningful semantics beyond the schema by explaining why country matters ('so the Stripe account opens in the seller's own country') and by clarifying the Stripe/USDC fallback behavior. It also reinforces the optional api_key linking behavior, adding value over the raw parameter descriptions.

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 action and resource: 'Become a seller of any asset type' and clarifies it 'Registers (or links) a seller account and returns a Stripe Connect onboarding link.' It distinguishes itself from siblings by naming list_health_data as the path for selling one's own health data and by focusing on account registration rather than listing or selling.

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?

The description gives clear context: Stripe is only for priced listings, free listings should skip it, and sellers outside Stripe countries should use USDC payout-wallet endpoints instead. It also names list_health_data as the alternative for own health data. It does not explicitly contrast become_seller with sell_data or seller_dashboard, but the registration-vs-listing distinction is implied strongly enough.

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