okx_get_profit_sharing_total

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

No annotations are provided to indicate traits like read-only or destructive behavior. The '[L:READ]' tag is informal and not part of the standard annotation set. The description lacks details on return format, safety, or side effects.

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 and contains no fluff, but it is excessively terse and lacks critical information. It is efficient but not well-structured for comprehension.

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 complexity of the tool ecosystem (many sibling copy-trading tools) and the absence of an output schema, the description is severely inadequate. It does not explain what the tool returns or how it relates to other profit-sharing tools.

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 covers 100% of parameters, so the description adds no extra value. The schema already documents the 'instType' parameter with its enum values. Baseline score maintained.

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 does not explicitly state the tool's purpose; it only provides a category and a prerequisite. The name suggests retrieving profit sharing totals, but without differentiation from siblings like 'okx_get_profit_sharing_details'.

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 mentions a prerequisite ('agent_catalog' should be called first) but offers no guidance on when to use this tool versus alternatives. There is no explicit context for selection.

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