okx_convert_contract_coin

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

No annotations are provided, and the description offers no behavioral disclosure. It does not indicate whether this tool is read-only, destructive, or has specific side effects, quotas, or security implications.

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, but it is under-specification rather than genuine conciseness. It lacks essential information and is not structured effectively to aid an AI 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?

For a tool with 4 required parameters, no output schema, and no annotations, the description provides almost no context. It directs users to call agent_catalog, but fails to explain the tool's functionality, return values, or use cases. This is completely inadequate.

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 each parameter has a description in the schema. However, the tool description itself adds no additional meaning or context beyond what the schema already provides. Baseline score of 3 applies as the schema carries the full burden.

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 is merely '[L:READ] CAT:[公共] | → 请先调用 agent_catalog', which does not state the tool's purpose. The name suggests converting contract coin, but no explicit verb or resource is provided, and it fails to distinguish from sibling convert tools like okx_convert_trade.

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. The instruction to call agent_catalog first is a prerequisite, not a usage guideline. There is no mention of scenarios, exclusions, or relationships to other tools.

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