chainvectorPredictionsTrades

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

With no annotations, the description must carry the full burden of behavioral disclosure. It describes the data nature (taker tape, YES vs NO lifts) but does not explicitly state that it is a read-only query, the return format, or whether results are ordered/aggregated beyond the 'limit' parameter. This is adequate but not fully transparent.

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 sentence that front-loads the core concept ('taker tape') and elaborates with key details (YES vs NO, price, order-flow context). No wasted words; it is easily scannable and appropriately sized.

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 simple read-only data tool with no output schema, the description covers the essential 'what' (taker tape, YES vs NO, price) and the context (order flow). It could mention whether it returns raw trades or aggregated data, or how rows are ordered, but given the low complexity, this is nearly complete.

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 100%, with all three parameters documented (series, limit, venue). The description adds no extra meaning beyond the schema—'across a series' simply reinforces the series parameter. Baseline 3 applies because the schema already handles parameter semantics.

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 identifies the tool's function: it provides prediction-market taker tape for a series, showing who is lifting YES vs NO at what price. This specific verb+resource framing distinguishes it from sibling tools like quotes (passive) or markets (listings), making the 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?

The phrase 'Order-flow context for an outcome' gives clear context for when to use the tool—when analyzing aggressive order flow in prediction markets. However, it does not explicitly name alternatives or state conditions like 'use this instead of quotes for aggressive flow,' so it lacks explicit exclusions.

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