Buy per-query access to live data listings — first taste free via data_preview. Requires an agent API key (Authorization: Bearer or X-API-Key). Open a prepaid buyer session against a public data listing. Not guest-callable. REST: POST /api/v1/data-sessions.
| Name | Required | Description | Default |
|---|---|---|---|
| listing_id | Yes | ||
| max_queries | No | ||
| open_tx_hash | No | ||
| buyer_address | Yes | ||
| proof_escrow_id | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds meaningful behavioral context beyond the annotations: the operation is paid/prepaid, requires an API key, and cannot be called by guests. It also gives the REST endpoint. Nothing contradicts the annotations, which already indicate this is a write operation.
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 short and front-loaded with the core purpose, then adds authentication and endpoint details. Minor redundancy exists between 'Buy per-query access' and 'Open a prepaid buyer session', but every sentence contributes useful information.
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?
The description covers purpose, auth, guest restrictions, and endpoint, but omits return values and does not explain the required parameters. Since there is no output schema and schema description coverage is 0%, this is a notable gap for an agent deciding how to invoke the tool correctly.
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?
With 0% schema description coverage, the description carries the burden of explaining parameters, but it only hints at them ('live data listings' suggests listing_id, 'per-query' suggests max_queries). It does not explain buyer_address or the remaining parameters, leaving the agent to guess their meaning.
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 a specific action, 'Open a prepaid buyer session against a public data listing', and identifies the resource as live data listings. It also distinguishes itself from the sibling data_preview by framing it as the free alternative, so an agent can tell these tools apart.
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 explicit conditions: it says to use data_preview for a free first taste, requires an agent API key, and notes it is 'Not guest-callable'. However, it does not contrast with the other lifecycle siblings like data_session_fund or data_session_query, so the guidance is partial.
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_* cluster has six closely related purchase-stage tools, and a2awire_guide/get_recommended_action/onboard_start all provide orientation guidance, creating some overlap. However, the descriptions are detailed enough to distinguish most tools, and the buyer vs. seller agent tools are fairly clear.
Most tools follow a readable snake_case verb_noun pattern such as check_earnings, discover_agents, and verify_contract, with a consistent data_session_* prefix. Exceptions like a2awire_guide and data_preview are noun-first, and hire_and_execute is a compound verb, so the pattern is not fully uniform.
Sixteen tools is borderline heavy, and the set includes a lot of A2AWire agent-marketplace plumbing that is not obviously needed for a server named after US economic releases. The data-session purchase flow is well represented, but many tools feel like platform infrastructure rather than focused economic-data functionality.
The per-query purchase flow is covered (preview, open, fund, attach escrow, query), but there is no obvious way to discover or list available CPI/Payrolls/Fed data listings. Session management is also thin, with no close, refund, or balance-inspection tool, and no direct economic-release-specific query surface.