create_limit_order

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

Discloses collateral lock amount (~0.957 ALGO, refundable), return value (escrowAppId), and suggests saving it for cancel_order. This provides essential behavioral context beyond a simple 'place order' statement, especially given no annotations.

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?

Three tightly written sentences: purpose, unit explanation with collateral info, and return value instruction. No fluff, front-loaded with key 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?

Covers all 5 parameters (via schema), explains units, collateral, and return value. No output schema exists, but description tells the agent what to expect. Minor gaps: no mention of balance requirements or order lifecycle post-placement.

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?

Adds concrete examples for price and quantity (e.g., '500000 = $0.50'), clarifying the microunits concept beyond the schema descriptions. While 100% schema coverage provides baseline, the examples significantly enhance understanding.

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 action ('Place'), the resource ('limit order on a prediction market'), and includes specific details about units and return value. This distinguishes it from sibling tools like create_market_order or cancel_order.

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 use for limit orders that require collateral and can be cancelled, but does not explicitly compare to alternatives like market orders or provide when-not-to-use scenarios.

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