Scaffold createOrder calldata

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

With no annotations, the description carries the safety burden. It discloses that the output is unsigned (implying no submission) and that the tool is prototype-only. However, it does not explicitly state whether the tool has side effects, validates inputs, or what errors may occur.

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 short sentences, each carrying distinct information: prototype status, core output, preconditions, and production alternative. No redundancy or 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?

The description covers the tool's workflow position and prototype status, but leaves gaps in parameter formats, output details, and error behavior. For a tool with no annotations and no output schema, this is insufficient for an agent to call it correctly without additional investigation.

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 description coverage is only 40%, and the description adds nothing about price, venue, timeInForce, or expirationAt formats. Required parameters like price are undocumented in both the schema and the description, so an agent cannot infer the expected string representation.

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?

States a specific verb and resource: 'Returns unsigned createOrder calldata.' The 'PROTOTYPE ONLY' warning and the sibling build_deposit_tx make its role unambiguous and distinct.

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 instructs to 'Run simulate_order and check_can_place_order first,' giving a clear precondition and ordering. Also states when not to use it ('Production bots encode via the npm ABI packages'), which routes production usage away from the tool.

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