okx_precheck_delta_neutral

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

The description includes '[L:READ]' hinting at read-only behavior, but no annotations are provided to reinforce this. There is no disclosure of behavioral traits such as required authentication, rate limits, or side effects. The description lacks specificity about what happens when the tool is invoked.

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 is concise, but at the expense of clarity. It is front-loaded with symbols that are not self-explanatory. While brevity is valued, the description should be informative. It earns a 3 as it is minimally adequate but not well-structured for an agent.

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 no parameters and no output schema, the description still fails to explain what the tool does or what its output represents. The instruction to call 'agent_catalog' first suggests a prerequisite, but the overall purpose and behavior are not covered. The description is incomplete for an agent to use this tool effectively.

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?

The input schema has no properties, so baseline is 4 per instructions. The description does not add parameter information, but since there are no parameters, no additional clarification is needed.

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 is cryptic and fails to state what the tool does. It includes symbols like '[L:READ]' and 'CAT:[账户]' which are not explained, and the main content instructs to call 'agent_catalog' first, leaving the actual function unclear. The tool name 'precheck_delta_neutral' suggests a pre-check for delta neutral strategies, but the description does not confirm this.

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 provides a prerequisite ('请先调用 agent_catalog'), which is a form of usage guidance, but it does not explain when to use this tool versus alternatives. There is no context for deciding to invoke this tool over sibling tools, and the 'when-not' scenarios are absent.

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