okx_get_signal_bots_pending

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

No annotations exist, so the description must disclose behavior. It only includes '[L:READ]' (possibly indicating read-only) and a category, but does not describe side effects, authentication needs, rate limits, or any behavioral traits beyond the implied read operation.

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, but it is in Chinese, uses symbols, and lacks structure. While concise, it under-specifies the tool's purpose and behavior, making it less helpful 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?

Given the lack of output schema, the tool's complexity (signal bots), and the minimal description, the description is severely incomplete. It does not explain return values, pagination, connection to agent_catalog, or any other contextual details needed for proper use.

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%, so the schema documents both parameters (algoId, instType). The description adds no additional meaning beyond the schema, earning a baseline score of 3.

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 tool name suggests retrieving pending signal bots, but the description ('[L:READ] CAT:[策略-信号] | → 请先调用 agent_catalog') is vague and in Chinese. It does not clearly state what the tool does or what 'pending' means, relying heavily on the name.

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 ('call agent_catalog first'), which is a usage guideline, but it does not explain when to use this tool over siblings or alternatives. No context on appropriate scenarios.

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