okx_get_taker_flow_contract

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

The '[L:READ]' tag hints at read-only behavior, but no annotations are provided. The description does not disclose other behavioral traits such as data freshness, rate limits, or side effects, leaving the agent uninformed.

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 (one line with tags), which is under-specified rather than concise. It lacks essential information about the tool's function and usage.

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 absence of annotations and output schema, and with 4 parameters, the description fails to explain the tool's behavior, return value, or differentiation from numerous sibling tools. The prerequisite is noted but not elaborated.

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 4 parameters with 100% description coverage, so the description adds no additional semantics beyond what the schema already provides. The prerequisite is not parameter-related.

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 a tag '[L:READ]' to indicate a read operation and 'CAT:[统计]' for category, but does not explicitly state what the tool does. The tool name suggests retrieving taker flow for contracts, but the description lacks a clear purpose 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 provides a prerequisite ('→ 请先调用 agent_catalog'), but does not explain when to use this tool versus alternatives, nor does it specify any contextual conditions for use.

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