getPredictionOrderEstimate

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

No annotations provided, so description carries full burden. Discloses that Phase 1 supports only FOK orders, that unfilled FOK orders are cancelled entirely, and lists returned fields (estimatedCost, estimatedReceive, feeAmount, toWin).

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?

Well-structured with bullet points and bold emphasis. Front-loaded with purpose. Could be slightly more concise, but every sentence adds value and the structure aids readability.

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 prediction market estimation tool, the description covers required parameters, behavioral constraints (FOK-only), and what to show the user. Despite no output schema, it mentions key return fields. Complete for correct agent invocation.

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 has 0% description coverage, but description adds detailed semantics for side, amount, payTokenCode, and orderType. It explains side=1 is BUY (amount in USDC) and side=2 is SELL (amount in shares). eventId and tokenId are not explicitly described but context implies their purpose.

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 it estimates execution details for a prediction market order before placing. Distinguishes itself by emphasizing it's mandatory before any buy or sell, and provides explicit BUY/SELL parameter guidance.

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 says 'Mandatory before any buy or sell' and instructs the agent to show estimated results to the user. Provides clear parameter mapping for BUY vs SELL, and mentions supported order type (FOK only).

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