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

Annotations confirm a mutating, non-idempotent, non-destructive write, so the safety profile is partly covered. The description still adds real value beyond them: the simulated-funds guarantee ('no real funds are ever at risk') and the API-key auth requirement. It omits failure behavior and the idempotency affordance offered by client_order_id.

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?

Three short sentences with zero waste; the core action is front-loaded and the two follow-ups (fund safety, auth) are distinct, useful facts rather than padding.

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 nine-parameter mutation tool with no output schema, the description should say what is returned (position, fill price, order id) and how the idempotency and dry-run paths behave. Those gaps leave an agent underinformed despite the solid safety and auth statements.

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?

Nine parameters with only 56% schema description coverage, and the description explains none of them. Nothing is said about sl/tp semantics, trailing stops, leverage caps, or how dry_run interacts with the write. The heavy parameters are left entirely to the schema.

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 ('Open a simulated position') plus an execution detail ('at the live price') that implicitly separates it from the limit-order sibling paper_limit_order. It does not explicitly name that sibling or any other alternative, so the differentiation is inferable rather than stated.

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?

Usage is only implied: 'at the live price' signals market-style execution versus paper_limit_order, and the API key requirement is stated. There is no explicit when-to-use guidance, no note on prerequisites such as sufficient paper balance, and no routing rule to the limit or SL/TP siblings.

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