polymarket_place_market_order

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

The description includes a prominent CAUTION warning that this executes a REAL trade with REAL funds at market price, and explains the semantics of FOK vs FAK order types. It does not detail the return value or potential slippage, but the risk warning is a significant behavioral disclosure given no annotations exist.

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 clear intro, a caution, a parameter list, and examples. Every section serves a purpose, and the content is concise without unnecessary filler.

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?

While it covers all parameters and risk, it omits the response format (e.g., order ID or confirmation) and prerequisites like allowance, which are important for a trading tool with no output schema and no annotations. The examples and parameter details are strong, but these gaps reduce completeness.

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 fully compensates by explaining each parameter's role, especially the context-dependent meaning of 'amount' (USD for BUY, shares for SELL), and providing concrete examples. This adds substantial value beyond the raw schema.

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 'Place a market order on Polymarket for immediate execution' with a specific verb and resource, and distinguishes itself from siblings like polymarket_place_order (likely limit orders) by emphasizing 'market order' and 'immediate execution'.

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 implies usage for immediate execution and provides examples, but does not explicitly mention when to use this tool versus alternatives like polymarket_place_order for limit orders, nor does it mention prerequisites such as having sufficient allowance (update_allowance sibling).

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