place_order

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

Annotations already mark the action as destructive and non-idempotent, and the description adds meaningful context: it places real money, requires a previously previewed order, and rechecks guardrails. This goes beyond what annotations alone convey without contradicting them.

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 three short, information-dense sentences. The real-money warning is front-loaded, followed by the essential usage constraint and safety re-check. Every sentence earns its place with no repetition.

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 one-parameter action with a rich annotation set and an output schema, the description covers the prerequisite, the parameter source, and the safety implications. Nothing critical is missing for correct invocation.

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%, but the description compensates for the single parameter by explaining that confirmation_id comes from preview_order, is single-use, and expires. This gives the agent the key semantic constraints it needs to supply a valid value.

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: 'Send a previously previewed order to Trade Republic.' The 'REAL MONEY' warning and the reference to confirmation_id clearly distinguish this execution step from preview_order and cancel_order.

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 explicitly defines when the tool can be used: only with a confirmation_id from preview_order, and notes that the id is single-use and expires. It also warns that guardrails are rechecked before sending, giving the agent concrete preconditions and expectations.

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