Place order (agent wallet)

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

Disclosures beyond annotations: dry-run mechanism, irreversible real orders when submitted, builder fee attachment. Aligns with destructiveHint=true and readOnlyHint=false.

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?

Two focused sentences with a clear warning. Front-loaded purpose. Every sentence contributes, though slightly longer due to necessary risk disclosure.

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 submission flow, risk, builder fee, and testnet advice. With output schema present, return values are assumed documented. Adequate for a trading tool.

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 coverage is high (78%). Description adds global context (builder code, dry-run logic) but does not detail individual parameters beyond what schema provides. Baseline 3 is appropriate.

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 it places a limit or market perp order via the agent wallet with builder code. It differentiates from sibling tools (e.g., hl_twap_order for TWAP) by specifying the order type and dry-run feature.

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?

Provides explicit instructions: dry-run by default, submit with confirm=true and dryRun=false. Warns to test on testnet. Lacks explicit comparisons to siblings but context enough for correct use.

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