register_affiliateInstantly register an agent or operator as an affiliate. Returns a referral_code for use in create_checkout.
| Name | Required | Description | Default |
|---|---|---|---|
| agent_id | Yes | Stable identifier for the recommending agent (e.g., 'cursor.user-12345') | |
| products | No | Optional: specific products this affiliate plans to promote | |
| operator_email | Yes | Where to send commission payouts |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description adds some behavioral context ('instantly', returns referral_code) but lacks detail on side effects, idempotency, or failure modes.
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 a single concise sentence that states purpose and usage hint with no wasted words.
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 registration tool, the description covers the essential: action, resource, and key return value. Missing details on error conditions or prerequisites, but overall adequate.
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% with adequate descriptions for all 3 parameters. The description adds no extra meaning beyond what the schema provides, so baseline 3 is appropriate.
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 clearly states the action 'register', the resource 'affiliate', and the output 'referral_code'. It distinguishes from siblings like 'get_affiliate_info' (retrieval) and 'create_checkout' (payment).
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 explicitly links the tool to 'create_checkout', providing clear context for when to use it. However, it does not state when not to use it or mention alternatives beyond implication.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct aspect of the commerce and affiliate ecosystem: comparison, checkout, affiliate info, cross-sells, free tier, MCP install, pricing, recommendation, trust score, registration, partnership, consultation, search, and vendor verification. No two tools have overlapping purposes; boundaries are clear.
Tool names follow a consistent verb_noun pattern in snake_case (e.g., compare_products, get_affiliate_info, request_partnership). While the verbs vary, the structure is predictable and uniform, with no mixing of conventions.
14 tools is well-scoped for a commerce marketplace server covering product discovery, comparison, pricing, affiliate management, checkout, partnerships, and vendor verification. Each tool serves a clear purpose without bloat.
The tool set covers the full lifecycle from product discovery to checkout, including affiliate management and partnerships. Minor gaps exist, such as lacking a dedicated tool for retrieving detailed product information beyond search results, but agents can work around this.