okx_get_total_unrealized_profit_sharing

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

No annotations are provided, so the description must carry the full burden. It only labels the tool as read and gives a category, with no information on side effects, authentication, rate limits, or what data is returned. Completely insufficient.

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 and concise, but it relies on cryptic labels and a prerequisite note. While not verbose, it sacrifices clarity for brevity. Could be restructured for better readability.

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 output schema and no annotations, the description should explain what the tool returns and how it relates to sibling tools. It fails to do so, providing only a category label and a reference to agent_catalog. Incomplete for effective use.

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, and schema coverage is 100% trivially. The description does not add parameter meaning, but baseline for 0 params is 4. No deduction 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 uses labels '[L:READ]' and 'CAT:[策略-跟单]' to hint at read operation and copy trading category, but does not explicitly state that the tool retrieves total unrealized profit sharing. The name is descriptive, but the description lacks a clear verb+resource 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?

No guidance on when to use this tool versus alternatives like okx_get_unrealized_profit_sharing or okx_get_profit_sharing_total. The only instruction is to call agent_catalog first, but no context on when to choose this tool.

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