place_order

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

With no annotations provided, the description carries the full burden. It discloses the non-destructive dry-run default, the conditions required for real trading (env vars), the signing of builder code, and the price semantics. This is thorough and goes beyond a simple 'place order' statement, giving agents critical safety and operational context.

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 extremely concise, two sentences, with the most important information (dry-run default) front-loaded. Every sentence adds value, and there is no wasted text.

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 an output schema exists, the description does not compensate for the 0% parameter coverage. It explains dry-run behavior and price but omits essential details about token_id, side, size, and order_type. An agent would struggle to correctly fill all required parameters without additional documentation.

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?

The schema has 0% description coverage, so the description must compensate. It only clarifies the meaning of 'price' (implied probability) but leaves token_id, side, size, and order_type unexplained. This is a significant gap for an agent trying to populate these parameters correctly.

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 a specific action ('Place a limit order') and resource (an order). It distinguishes itself from siblings like cancel_order and open_orders simply by being the order-placement tool. The added detail about dry-run behavior further sharpens its purpose.

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 clear guidance on when to use it in dry-run mode versus real trading, explicitly requiring environment variables for live execution. It does not explicitly mention alternative tools, but since this is the only order-placement tool among the siblings (kalshi_place_order is for a different platform), the context is sufficient.

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