okx_get_lead_trader_positions

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

With no annotations, the description should disclose behavioral traits. It only has a '[L:READ]' tag (not official) and a category flag. It doesn't mention authentication, rate limits, or data scope. The prerequisite is noted 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 but it is not effectively concise because it misses critical functional details. It reads as a note rather than a proper description, wasting the opportunity to inform the agent.

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?

No output schema and no annotations; the description should cover what the tool returns and any prerequisites. It only mentions calling agent_catalog, but the rest of the context (e.g., return format, filtering) is absent. Incomplete for a tool with 2 parameters and a required one.

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?

Schema coverage is 100% so the baseline is 3. The description adds no additional meaning to the parameters beyond what the schema already provides. It does not explain how the parameters affect the results.

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 state what the tool does explicitly. It contains a category hint and a prerequisite note but lacks a clear verb+resource statement. The name suggests 'lead trader positions' but the description relies on that implicit understanding.

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 only mentions calling agent_catalog first but gives no guidance on when to use this tool versus alternatives like okx_get_my_lead_positions. No context on when to use or avoid this tool.

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