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

Annotations already cover mutability and idempotency, and the description adds useful behavioral context: API-key requirement, guest exclusion, the preference for open_tx_hash, and the paid nature of the access. No contradiction with the annotations exists.

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 concise and front-loaded: it states the value proposition, prerequisites, parameters, and REST endpoint in only four sentences. Each sentence conveys needed information without padding.

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 the lack of an output schema, the description covers the essential call context: endpoint, authentication, session prerequisite, and escrow options. A brief note about what happens after attaching escrow would round it out, but the purpose and siblings make it reasonably inferable.

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 only 33% schema coverage, session_id is documented in the schema, but open_tx_hash and proof_escrow_id are not. The description compensates by identifying them as escrow identifiers and stating open_tx_hash is preferred, though it leaves ambiguity about whether one of them is required.

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 action: attaching a buyer-funded proof escrow to an opened data session to buy per-query access. It also distinguishes itself from the free data_preview alternative, making the tool's purpose unambiguous.

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?

It specifies prerequisites (agent API key, opened data session, funded escrow), authentication methods, and that the tool is not guest-callable. It points users to data_preview for a free taste, which helps with selection, though it does not explicitly contrast with data_session_fund or funding_package.

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