executePredictionSell

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

No annotations provided, so description carries full burden. It discloses FOK behavior (cancelled if not fully filled), async nature (response is ACK, check getPredictionOrderList), and slippage tolerance. However, it does not explicitly describe failure modes or side effects beyond the exchange, though it is implied.

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?

Description is well-structured with headers (Prerequisites, Do NOT call, Phase 1, Response, Agent hint) and front-loaded purpose. Some redundancy exists between the main description and the 'Agent hint' section, but it remains clear and organized.

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 no output schema, the description explains the ACK response and async verification via getPredictionOrderList. It covers prerequisites, limitations, and the FOK-only constraint. While it lacks explicit error handling details, it is sufficiently complete for a transactional tool with clear steps.

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 coverage is 0%, so description must compensate. It explains size (shares, not USDC), slippage (price tolerance as string), and orderType (1 = FOK only). However, tokenId, eventId, and toTokenCode are not described. Three out of six parameters are given meaningful context, but others are left to inference.

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 it 'Execute a sell order for prediction outcome tokens' and 'Exchanges token shares for USDC.' It uses specific verb and resource, and distinguishes from siblings by listing prerequisites that involve other prediction tools like getPredictionPositionList and getPredictionOrderEstimate.

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 provides explicit prerequisites with mandatory order: call getPredictionEngineStatus, getPredictionPositionList, getPredictionOrderEstimate first. It also states 'Do NOT call this endpoint without explicit user confirmation.' and clarifies that only orderType=1 (FOK) is supported.

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