okx_get_affiliate_performance

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

No annotations are provided, so the description bears full burden. It includes [L:READ] indicating read-only, but does not disclose other behavioral traits such as required permissions, response format, or side effects. The description is insufficient for safe agentic invocation.

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 sacrifices clarity for brevity. It includes a label and a prerequisite, but lacks a clear statement of tool purpose. It is concise but not well-structured for usability.

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 no parameters and no output schema, the description needs to explain the tool's core functionality. It fails to do so, merely hinting at a category and a prerequisite. The tool's purpose and return value remain unclear.

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 no parameters (100% coverage trivially). With zero parameters, the baseline is 4, but the description adds no parameter semantics. However, since schema coverage is high, a baseline 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 only provides a category (CAT:[推广]) and a prerequisite ('请先调用 agent_catalog'), but does not state what the tool does with a verb and resource. It is vague and fails to differentiate from sibling tools like okx_get_affiliate_invitee_list.

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 instructs to call agent_catalog first, which is a prerequisite, but provides no guidance on when to use this tool versus alternatives. There are no explicit when-to-use or when-not-to-use conditions.

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