okx_get_unrealized_profit_sharing

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 includes '[L:READ]' hinting at read-only behavior, but lacks disclosure about authentication, rate limits, side effects, or data presentation. Minimal transparency 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 brief but not concise in a helpful way. It uses cryptic tags and a prerequisite note without structuring information clearly for an AI agent. It could be more readable.

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 lack of output schema and vague description, the tool is incomplete. It does not explain what the response contains, how to interpret results, or how it differs from related tools like okx_get_total_unrealized_profit_sharing.

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 zero parameters, so schema coverage is 100%. The description adds no meaning beyond the schema, but baseline for 0-parameter tools is 4. No param info needed.

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 'L:READ' and 'CAT:[策略-跟单]' suggest it's a read operation in the copy trading category, but it does not explicitly state that the tool retrieves unrealized profit sharing details. The purpose is implied by the name but not clearly articulated.

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 instruction '请先调用 agent_catalog' indicates a prerequisite (call agent_catalog first), but it does not provide guidance on when to use this tool over alternatives (e.g., okx_get_total_unrealized_profit_sharing) or when not to use it.

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