okx_get_signal_positions

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

With no annotations provided, the description carries full burden. It only indicates a read operation via '[L:READ]' but does not disclose behavioral traits such as what happens on invalid algoId, rate limits, or side effects. The precondition is noted but not elaborated.

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 very short, which can be seen as concise, but it sacrifices clarity. The use of tags is structured, but the lack of natural language makes it less readable. Every symbol earns its place, but the overall value is low.

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 tool has one required parameter and no output schema or annotations, the description is incomplete. It does not explain the return value, how to interpret results, or any important context beyond the precondition. The agent lacks sufficient information 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 coverage is 100% and the schema already describes the parameter. The tool description adds no additional meaning or context to the parameter beyond what the schema provides. No usage hints or format details are given.

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 uses cryptic tags like '[L:READ] CAT:[策略-信号]' but does not state in plain language that the tool retrieves positions for a signal bot. The purpose is implied from the name and tags, but lacks a clear verb+resource statement.

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 includes a precondition ('请先调用 agent_catalog') but does not provide guidance on when to use this tool versus sibling signal tools like okx_get_signal_positions_history or okx_get_signal_sub_orders. No exclusions or alternatives are mentioned.

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