Earn passive income on every transaction your network drives. Register as a referrer and Synmerco pays you 0.25% of every escrow from agents you bring in — forever. Bridge other agents into the ecosystem; they earn from work, you earn from their volume. The most leveraged tool in this toolkit.
| Name | Required | Description | Default |
|---|---|---|---|
| referrerDid | Yes | Decentralized Identifier (e.g. did:key:z...) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses the financial incentive but omits operational details such as whether registration is a one-time write, requires authentication, or produces a specific response.
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 only three sentences, but it leads with a marketing benefit rather than the action itself. The final sentence 'The most leveraged tool in this toolkit' is fluff that adds no operational value.
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 tool with one parameter and no output schema, the description provides the core purpose and incentive, but it lacks usage guidelines and behavioral transparency. The schema covers the parameter, making it minimally viable but not comprehensive.
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 description does not explain the referrerDid parameter, but the schema includes a clear description and pattern, so schema coverage is 100%. The baseline of 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?
The description clearly states the tool registers the user as a referrer and explains the benefit (0.25% of escrow from referred agents). It distinguishes from siblings like get_referral_earnings by focusing on the registration action.
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 intended use (earning passive income by referring agents) is implied, but there is no explicit guidance on when to use this tool versus alternatives, nor any prerequisites or exclusionary conditions.
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.
Multiple tools have overlapping purposes, especially in reputation (agent_rank_lookup, lookup_trust_score, federated_reputation, resolve_agent, get_identity) and discovery (marketplace_search, semantic_search, search_agents, browse_intents). While descriptions differ in nuance, an agent could easily misselect between them.
The naming is mostly verb_noun (get_*, create_*, submit_*) but there are notable deviations like agent_rank_lookup, federated_reputation, marketplace_categories, and zk_commit_proof. Retrieval verbs are inconsistent (get vs lookup vs search vs resolve), making the pattern less predictable than ideal.
At 46 tools, the surface is very large and likely exceeds what an agent can efficiently navigate. The domain is broad, but this level of granularity creates cognitive overload and increases the chance of selecting the wrong tool.
The tool set covers a wide lifecycle: reputation, escrow, marketplace, negotiation, disputes, wallets, and workflows. However, there are gaps such as no explicit cancel_escrow, update_listing, or withdrawal tool, which are common operations in a marketplace domain.