getPredictionOrderList

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

No annotations are provided, so the description carries full burden. It discloses that FOK orders show as FILLED or CANCELLED, and lists filtering parameters with their meanings. It does not mention rate limits or pagination details, but overall adequately describes behavior.

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 well-structured: clear purpose, return details, usage context, parameter list, and agent hints. Every sentence adds value, and it is front-loaded with the main operation.

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?

There is no output schema, but the description mentions return details (fill status, executed price, fees). It covers all key parameters and usage scenarios. Given 7 parameters and 0 required, this is a complete and helpful description.

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 0%, so the description must compensate. It explains the meaning of status (with enum mappings), tokenId, eventId, side, and days (max 90). However, it does not explain pageIndex or limit, leaving some parameter semantics missing.

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 tool queries the authenticated user's prediction market order history, with a specific verb ('Query') and resource ('prediction market order history'). Among many sibling 'get' tools, this distinguishes itself by focusing on prediction orders.

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 says 'Use this after placing a buy or sell order to check the final execution status,' providing clear when-to-use guidance. It also gives agent hints about filtering. It does not explicitly list alternatives, but the context is strong.

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