okx_get_signal_sub_orders

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

No annotations are present, so the description carries the full burden. It includes a non-standard '[L:READ]' prefix hinting at read-only behavior, but does not disclose other behavioral traits such as required permissions, data scope, or side effects. The description adds minimal value beyond the name.

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 fails to convey sufficient information. While it is front-loaded with the READ prefix, it does not earn its place because it omits essential details about the tool's function. It is under-specified rather than concise.

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's moderate complexity (no output schema, no annotations, many sibling tools), the description is critically incomplete. It does not explain what sub-orders are, how they relate to signal bots, or what the response contains, leaving the agent without necessary context to use the tool correctly.

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% with both parameters described, so baseline is 3. The description does not add any additional meaning or context beyond what the schema provides, so no extra credit.

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 does not explicitly state what the tool does. It only provides a category label and a prerequisite, relying on the tool name to imply purpose. This is vague and insufficient for an AI agent to understand the action.

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 only mentions a prerequisite to call 'agent_catalog' first, but does not explain when to use this tool versus other signal-related sibling tools (e.g., okx_get_signal_orders, okx_get_signal_positions). No context for selection is provided.

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