Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations, the description adds meaningful behavioral context: it requires a specific auth mechanism, is not guest-callable, uses REST GET, and returns instructions/calldata rather than performing the funding action itself. This gives an agent a clear model of side effects, consistent with readOnlyHint and idempotentHint.

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?

Every sentence carries unique, decision-relevant information: purpose, free alternative, auth requirement, return value, guest restriction, and exact endpoint. It is front-loaded with the core purpose and contains no filler.

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 single-parameter, read-only, idempotent tool with no output schema, the description covers the essential invocation context: session prerequisite, auth, REST route, and return content. It is complete enough for an agent to select and call this 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?

The schema already provides 100% coverage for the single session_id parameter, including its UUID format and provenance from data_session_open. The description only repeats that it applies to an opened data session, adding no new parameter-level meaning beyond the schema.

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 purpose: buying per-query access to live data listings, and clarifies exactly what the tool returns: earnings-wallet funding instructions and createEscrow calldata. It distinguishes itself from data_preview by calling it a free taste and from other data-session siblings by targeting an already-opened session.

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 routes users to data_preview for a free taste, states that the tool requires an agent API key, says it is not guest-callable, and scopes usage to an opened data session. This provides clear when-to-use and when-not-to-use guidance relative to the sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.