avanza_open_order_edit

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

With no annotations provided, the description carries the behavioral burden. It transparently discloses that the tool can dry-run or live-update, that live updates mutate state, and that confirm=true plus TUI R/W mode are required for a real change. It does not describe return values or reversibility, but the core safety-relevant behavior is clearly stated.

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 dense sentences with no filler. The primary purpose and the critical confirmation requirement are front-loaded, and the alias note is concise and 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?

For an 8-parameter mutation tool with no annotations and no output schema, this description is too sparse. It omits expected formats for valid_until and price, what dry-run actually returns, likely error conditions, and post-update behavior. The agent would need to inspect sibling tools or external docs to call this correctly.

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 25%, and the description does not compensate for the undocumented fields. It usefully ties confirm to live updates, but leaves price, volume, and valid_until semantics unexplained, forcing the agent to guess formats and units.

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 uses a specific verb and resource: 'update an existing open/pending regular order,' with a clear dry-run versus live-update distinction. It also states it is an alias of avanza_order_edit, which orients the agent, though it does not fully distinguish behavior from that sibling.

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 implies the tool is for editing existing open/pending orders and states the necessary condition for a live update: TUI R/W mode and confirm=true. However, it does not explicitly say when to prefer this over avanza_order_edit, avanza_order_set, or avanza_open_order_cancel.

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