Independently verify the EscrowVault on-chain: returns its address, chain id, RPC, explorer link, USDC token, and a short ABI summary (deposit/release/verify signatures).
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| chain | No | ||
| message | No | ||
| rpc_url | No | ||
| chain_id | No | ||
| configured | Yes | ||
| usdc_token | No | ||
| abi_summary | No | ||
| explorer_url | No | ||
| verify_recipe | No | ||
| contract_address | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that verification is performed on-chain and lists the returned data, but it does not disclose additional behavioral details such as error conditions, external call side effects, or authorization requirements beyond what the annotations already capture.
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, front-loaded sentence with no filler. It leads with the verb and resource, then presents a compact, scannable list of return values, making efficient use of the available space.
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?
With zero parameters, rich annotations, and an output schema present, the description is complete enough for correct invocation. The description adds a useful summary of the returned data, while the output schema covers the formal return structure.
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 tool has zero parameters, and the input schema explicitly states 'No arguments' with 100% schema coverage, so there is no parameter ambiguity for the description to resolve. The baseline of 4 for zero-parameter tools 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 opens with a specific verb ('verify') and a clear resource ('EscrowVault on-chain'), then enumerates the exact return values: address, chain id, RPC, explorer link, USDC token, and ABI summary. This level of specificity clearly differentiates it from sibling tools like data_session_fund or get_agent_contract.
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 states what the tool does but never says when to prefer it over alternatives or when not to use it. No sibling tools or exclusions are mentioned, so an agent must infer usage context from the tool name alone.
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.
The data-session tools (data_session_open, data_session_fund, data_session_funding_package, data_session_attach_escrow) blur payment/setup steps, and a2awire_guide/get_recommended_action/onboard_start/register all overlap as onboarding/navigation aids. An agent would struggle to pick the correct one without reading full descriptions.
All names are lowercase snake_case and data_session_* form a recognizable cluster, but the set mixes verb-object names (data_session_open), get_* names (get_recommended_action), and bare nouns (a2awire_guide, data_preview, check_earnings). There is no single predictable convention across the server.
Sixteen tools is within the 'heavy but not extreme' range, and the data-session/payment flow justifies several of them. Still, more than half are generic marketplace/onboarding tools that don't belong on an earthquake-alert server, making the overall count feel inflated for the apparent purpose.
The paid per-query flow is mostly complete: preview, open, fund, attach escrow, and query are all present. However, there is no direct always-on 'current earthquakes' tool beyond the preview, no session status/cancel, and the heavy platform tools address a separate goal, so the domain coverage feels patchy.