okx_run_single_agent

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

No annotations are present, so the description must disclose behavioral traits itself. It only states that it 'runs' the agent and returns a report, with no mention of side effects, permissions, costs, or limitations. This is insufficient for a tool that executes AI analysis agents.

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 three short sentences with no fluff, front-loading the core action and then adding a benefit and output. Every sentence contributes value.

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?

For a tool with four parameters, a nested object, and no output schema, the description is too sparse. It omits how to construct enabledSkills, what instType/instrument refer to, and what the report contains. The lack of annotations further increases the need for a richer description.

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 description adds meaning by listing the three agent types (macro, technical, risk) which aligns with the agentId enum, but it does not explain instType, instrument, or enabledSkills. With only 50% schema description coverage, the description fails to compensate for the undocumented parameters.

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 clearly states 'Run a single AI analysis agent' with the agent types parenthetically listed. It contrasts with 'full co-pilot', distinguishing it from the sibling okx_run_copilot. This satisfies a specific verb+resource+scope.

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 phrase 'Faster than full co-pilot' provides some context for when to prefer this tool over okx_run_copilot, but it does not specify when not to use it or mention alternative tools like okx_technical_analysis. The guidance is implied rather than explicit.

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