order

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

With no annotations, the description offers no behavioral transparency. It doesn't disclose side effects, execution semantics, authentication requirements, or whether this is a real trade order. The only implication is that it creates an order, which is minimal.

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 a single sentence, which is concise but underspecified for a tool with 11 parameters. It lacks structure or additional context, but it is not verbose. Under-specification makes it less useful.

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 tool has 11 parameters, no output schema, and no annotations. The description is only one sentence, leaving out critical information about order execution, return value, risk, and usage context. This is highly incomplete.

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 0%; the description does not explain any of the 11 parameters. Param names like 'is_buy' and 'limit_px' are partially self-explanatory, but the description adds no semantics, default values, or relationships.

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 the action (Place an order) and the platform (Hyperliquid), distinguishing it from sibling tools like cancel_order and get_order_status. It lacks specifics on order types or asset classes, but the core purpose is unambiguous.

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 no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. It simply states the action without context.

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