okx_get_signal_orders

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

No annotations are provided, so the description bears full responsibility. It only declares '[L:READ]' (likely read-only) and a category, but omits critical behavioral details such as authentication requirements, error handling, or side effects. This is completely inadequate for a tool that likely involves retrieving order data.

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 extremely short but not effectively concise because it uses cryptic codes like '[L:READ] CAT:[策略-信号]' instead of plain language. It lacks structure and front-loads no useful information for an AI 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?

For a simple tool with one parameter and no output schema, the description should at least state what the tool returns and when to use it. It fails to provide any such context, leaving the agent without enough information to decide on 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?

The input schema covers the only parameter (algoId) with a description in Chinese meaning 'signal bot ID, required'. Since schema coverage is 100%, the description adds no additional value for parameter semantics. Baseline score of 3 is appropriate.

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: '[L:READ] CAT:[策略-信号]' does not explicitly state what the tool does. The tool name 'okx_get_signal_orders' hints at retrieving signal orders, but the description fails to provide a clear verb+resource. It also does not differentiate from sibling tools like okx_get_signal_bots_pending or okx_get_signal_positions.

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 gives a prerequisite instruction ('请先调用 agent_catalog') but does not specify when to use this tool versus alternatives. No comparisons or exclusions are provided, leaving the agent uncertain about when this tool is appropriate.

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