avanza_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 discloses that the tool supports dry-run versus live update, that confirm=true gates the live update, and that TUI R/W mode is a prerequisite. This goes well beyond a bare 'edit order' statement, though it does not detail response behavior or failure modes.

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?

A single dense sentence that front-loads the core action, then adds the critical condition for live execution. Every clause carries meaningful information; there is no filler or redundancy.

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 definition covers the essential behavioral modes and prerequisites despite lacking annotations and an output schema. It does not describe return values or error conditions, but for selecting and invoking the tool, the required parameters and the dry-run/live distinction are sufficiently specified.

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%, but the description compensates for the key editable fields by naming price/volume/valid_until and explaining confirm's role in switching from dry-run to live update. However, account_id and order_id semantics are left implicit, and valid_until's format is unspecified.

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 tool edits an existing open order's price/volume/valid_until, and distinguishes 'dry-run' from 'live update'. The phrase 'existing open order' differentiates it from siblings like avanza_order_set (creating orders) and avanza_open_order_cancel/avanza_order_delete (removing orders).

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?

It gives explicit context: this is for editing existing open orders, and live execution requires TUI R/W mode plus confirm=true. It does not explicitly name alternative tools for exclusion, but the intended use case is clear enough for an agent to route correctly.

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