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

The description discloses the paid nature (0.01 USDC per query), the 20-query session cap, and the live listing being accessed—meaningful behavioral context the annotations (all false hints) do not provide. It does not cover receipt handling or failure behavior, so it stops short of a 5.

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 clause earns its place: pricing, query limit, the preview alternative, and the prerequisite sequence are compressed into a few front-loaded lines with no filler. The sequence notation makes operational order instantly parseable.

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 the payment model, rate limit, and required open/fund flow, but it is incomplete for a 5-parameter paid tool with no output schema because query and k semantics are left unspecified. The schema covers session_id and receipt options, making this minimally viable with notable gaps.

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?

Schema description coverage is only 40%, and query and k have no meaningful semantic descriptions. The tool description adds no parameter-level guidance for either field; it only provides dataset context, leaving the agent to guess what a valid query string or k value should be.

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 frames data_session_query as the terminal step in the open→fund→query sequence and names a specific paid listing with per-query pricing, so an agent can distinguish it from data_preview and data_session_fund. It does not literally say 'run a query' until the schema description, but the sequence and billing context make the action identifiable.

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 explicitly gives the prerequisite sequence (data_session_open → data_session_fund → data_session_query) and points to data_preview for a free first taste, which tells an agent when to choose this tool over its sibling. It lacks an explicit 'do not use when...' clause, but the flow and pricing communicate appropriate usage well.

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