avanza_paper_order_set

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 clearly states that no Avanza order is placed and that the operation is allowed in MCP read-only mode, which is a critical safety trait. It does not describe local state persistence, validation behavior, or order lifecycle, so it is not a 5.

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 sentences with no filler. The core action is front-loaded, and the most important safety distinction—'never places an Avanza order'—appears in the second sentence with maximum clarity.

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 14-parameter tool with no output schema and no parameter documentation, this description is too thin. It provides useful safety context but leaves the agent to infer required field formats, how paper orders are handled, how this relates to paper exits/stoplosses, and what a successful call returns.

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%, and the description adds no parameter-level meaning. The phrase 'buy/sell' hints at order_type, but the agent gets no help with price, volume, valid_until, stop_price, target_price, session_id, condition, or fill_immediately.

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 specific verb and resource: 'Create a local paper buy/sell order.' It also explicitly distinguishes itself from real-order tools like avanza_order_set by saying 'This never places an Avanza order,' and it is clearly distinct from paper stoploss and paper exit siblings.

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 gives clear context: use this for local paper orders, not live Avanza orders, and it is safe in MCP read-only mode. However, it does not explicitly name the live-order alternative or state when not to use it beyond the 'never places an Avanza order' exclusion.

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