avanza_order_set

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

With no annotations, the description carries the behavioral disclosure burden. It reveals a critical safety gate for live orders: R/W mode plus confirm=true. But it does not describe what a dry-run returns, what happens on validation failure, or other execution-side behaviors.

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, front-loaded with the primary purpose and followed by the essential safety condition. There is no filler or repetition of schema content.

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 a 10-parameter mutating order tool with no annotations and no output schema, this is incomplete. It omits dry-run output behavior, valid_until format, and routing guidance to the paper-trading sibling avanza_paper_order_set.

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 20%, so the description must compensate for the undocumented required parameters. It clarifies confirm's role and order side, but leaves account_id, order_book_id, price, valid_until, volume, and condition without added meaning.

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 states a clear verb and resource: dry-run or place a regular buy/sell order. It is specific enough to distinguish it from stoploss and order-management siblings, though it does not explicitly differentiate from avanza_paper_order_set.

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 provides actionable context: dry-run is available generally, while live placement requires TUI R/W mode and confirm=true. However, it does not explicitly state when to prefer this tool over alternatives such as avanza_paper_order_set or avanza_order_edit.

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