convert_position

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

No annotations are provided, so the description must disclose behavior. It states the core action but omits important side effects such as whether the original position is closed, whether margin or funds are affected, whether the conversion is reversible, or what the response indicates. For a mutating tool, this is a significant transparency gap.

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 a single, front-loaded sentence with no wasted words. It is concise, though it may be too brief for an 8-parameter mutation operation that lacks parameter documentation.

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?

Given the complexity of position conversion, the lack of annotations, and the high number of undocumented parameters, the one-sentence description is insufficient. It does not explain preconditions, allowed product types, response behavior, or how to identify the position being converted, making it incomplete for reliable 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%, so the description needs to compensate. It only clarifies the meaning of oldproducttype and newproducttype via the example, leaving exchange, symboltoken, tradingsymbol, transactiontype, quantity, and type unexplained. The example adds some value but does not cover the majority of required parameters.

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 identifies the verb ('Convert'), the resource ('a position'), and the transformation ('from one product type to another'). The example INTRADAY -> DELIVERY makes the operation instantly understandable and distinguishes it from order placement/modification tools.

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 implies the use case—changing the product type of an existing position—but does not explicitly state when to use this tool versus place_order, modify_order, or get_positions. No exclusions or alternative tool names are provided, so the guidance is present only by inference.

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