hl_frontend_open_orders

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only hints at the return content ('trigger/TPSL-style visibility') but does not state whether the operation is read-only, what side effects may occur, or what the 'frontendOpenOrders' distinction implies behaviorally.

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 short, but the parenthetical '(frontendOpenOrders)' is redundant with the tool name and does not add clarity. The phrase is a fragment rather than a complete sentence, and a more direct construction would be equally concise.

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?

Although an output schema exists, the description fails to explain how this tool differs from the closely named sibling `hl_open_orders`, nor does it provide usage context for the parameters or any constraints. The description is too minimal to be considered complete for a tool in a large sibling family.

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 0%, and the description offers no explanation of the `user` or `dex` parameters. The agent receives no semantic guidance beyond the bare parameter names, which is insufficient for a low-coverage schema.

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 identifies the resource ('open orders') and differentiates itself from sibling `hl_open_orders` by mentioning 'trigger/TPSL-style visibility' and 'frontendOpenOrders'. However, it lacks an explicit verb like 'gets' or 'lists', making it slightly less clear than it could be.

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?

No guidance is given for when to use this tool versus alternatives like `hl_open_orders` or `hl_order_status_by_oid`. The description does not mention any context, prerequisites, or exclusions.

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