okx_get_co_inviter_list

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

No annotations are provided, so the description carries the full burden. It indicates read-only via 'L:READ' but does not disclose any other behavioral traits such as required permissions, rate limits, or side effects. The prerequisite hint is present but insufficient for full transparency.

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 (two lines) and front-loads the read indicator and category. However, it is terse and lacks explanatory structure. While concise, it sacrifices clarity for brevity.

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 large set of sibling tools and no output schema, the description is incomplete. It does not explain what the returned data contains, how the prerequisite agent_catalog relates, or what distinguishes this tool from similar ones. A more complete description is needed for a runtime environment without annotations.

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?

There are no parameters, so the input schema covers 100% of parameter definitions. The description does not need to add parameter info beyond what is already covered. Baseline for zero parameters is 4, and this tool meets that.

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 name clearly indicates 'get co-inviter list', and the description adds 'L:READ' and a category label, but does not elaborate on what the list contains or how it differs from sibling affiliate tools like okx_get_affiliate_invitee_list. The purpose is somewhat clear but not fully specified.

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 states to call agent_catalog first, which is a prerequisite guideline. However, it does not provide when to use this tool versus similar affiliate tools (e.g., okx_get_affiliate_invitee_list), nor any context about when it is appropriate or inappropriate.

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