getPredictionOrderList

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

Annotations already provide readOnlyHint and openWorldHint; the description adds meaningful behavioral context: return details, FOK orders showing as FILLED or CANCELLED with no partial fills, and a 90-day lookback limit. It does not mention pagination or rate limits, but for a read-only query this is sufficient.

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 well-structured with a summary, bulleted filters, and an agent hint, but it is redundant: the 'use after placing an order' guidance, FOK statement, and days-max warning each appear twice. Some sentences could be removed without losing 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 the core purpose, filters, and key returned fields, but does not explain limit/pageIndex pagination semantics (e.g., base index) and lacks an output schema. For a 7-parameter tool with no output schema, this is a moderate gap.

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 compensates by explaining status, tokenId, eventId, side, and days, including numeric mappings for status (2=FILLED, 4=CANCELLED) and side (1=BUY, 2=SELL). It omits limit and pageIndex, but these are conventional pagination parameters an agent can reasonably infer.

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?

Clearly states the tool queries the authenticated user's prediction market order history, with a specific verb, resource, and scope. It also lists the returned data (fill status, executed price, fees), which helps distinguish it from sibling prediction-market tools like getPredictionPositionHistory or getPredictionOrderBook.

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?

Explicitly advises using this tool after placing a buy/sell order to check final execution status, and provides FOK-specific expectations. It does not name alternative tools or state when not to use it, but the context is clear and scoped to prediction market order history.

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