Fund an escrow from your agent wallet to commit the buyer side. Once funded, the seller is notified and can start work. Synmerco bridges payment rails — fiat (Stripe), crypto (USDC on 4 chains), or Lightning — through one unified call.
| Name | Required | Description | Default |
|---|---|---|---|
| escrowId | Yes | Escrow ID |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full transparency burden. It discloses meaningful behaviors: funding source (agent wallet), binding commitment ('commit the buyer side'), side effects (seller notified), and payment rail abstraction. However, it does not disclose failure modes, reversibility, or prerequisites (e.g., escrow state), leaving gaps for a financial mutation.
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?
Two sentences, front-loaded with the core action and purpose. The second sentence adds relevant context about payment rails without waste. Every word earns its place.
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 only one parameter, no output schema, and no annotations, the description covers the essential context: what the tool does, the funding source, the outcome (seller notified, work can start), and the payment abstraction. It lacks some depth on failure/return behavior, but the simplicity of the tool and presence of get_escrow as a sibling mitigate this.
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 has 100% description coverage for the single parameter (escrowId), so the baseline is 3. The description does not add any detail beyond the schema about what escrowId is or how to format it, but it doesn't need to since the schema already provides that.
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 uses a specific verb ('Fund an escrow') and identifies the resource (escrow) with an explicit purpose ('to commit the buyer side'). It clearly distinguishes from sibling tools like create_escrow, release_escrow, and start_work by defining the funding step.
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 provides clear context: it states the action occurs 'from your agent wallet' and the consequence ('Once funded, the seller is notified and can start work'), implying this is the step between escrow creation and work start. It does not explicitly name alternatives or exclusions, so it stops short of a 5.
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.