close_position

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

The description adds the requirement for confirm=true, implying a sensitive/destructive operation. Since no annotations are provided, this is helpful, but it does not disclose other behavioral traits like irreversibility, permissions, or side effects on existing positions.

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 concise sentence with no fluff, front-loading the action and resource. However, it is too sparse, omitting crucial parameter context.

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?

With two parameters (one a nested object) and no schema descriptions, the description is insufficient for safe and correct invocation. The output schema exists but does not clarify the close_order parameter structure or usage.

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 must compensate. It explains that confirm must be true, but gives no information about close_order, which is a free-form object. This is a significant gap for correct invocation.

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 states the action ('Close') and the resource ('OTC positions'), specifying scope ('one or more'). It distinguishes the tool from siblings like create_position and update_position.

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?

No guidance on when to use this tool versus alternatives. The confirmation requirement ('confirm=true') is a prerequisite, but there is no mention of exclusions or when not to use the tool.

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