okx_get_signal_subscriptions

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

The '[L:READ]' tag indicates a read-only operation, which is helpful for behavioral transparency given the absence of annotations. However, the description provides no other behavioral details such as side effects, rate limits, or return structure, leaving the agent with minimal information beyond the read hint.

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 concise with a single line of codes and Chinese text. While it is front-loaded with the read flag, the cryptic style may reduce clarity for AI agents. It is efficient but sacrifices explicitness.

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 no parameters, no output schema, and no annotations, the description provides a prerequisite (call agent_catalog first) which adds some context. However, it does not describe the return data (e.g., list of signal subscriptions) or complete purpose, leaving gaps in contextual understanding.

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 tool has no parameters (schema coverage 100%), so the description does not need to add parameter information. The baseline score of 4 is appropriate as no additional semantic value is required.

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 codes like '[L:READ]' and 'CAT:[策略-信号]' and suggests calling agent_catalog first, but it does not explicitly state that the tool retrieves signal subscriptions. The purpose is vaguely inferred from the tool name and category, but lacks a clear, direct 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 prerequisite ('→ 请先调用 agent_catalog'), which gives some usage guidance. However, it does not specify when to use this tool versus other signal-related tools, nor does it provide any exclusion or alternative context.

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