okx_get_convert_estimate_quote

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

No annotations provided, so description carries full burden. It only hints at a read operation via '[L:READ]', but does not disclose behavioral traits like side effects, authentication needs, or rate limits. Agent gets almost no 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 an underspecified tag line, not a proper description. It fails to earn its place by providing minimal useful information.

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 tool has 3 required parameters and no output schema or annotations, the description is completely inadequate. It does not explain the return value, how to interpret the quote, or any usage context.

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% with clear descriptions for fromCcy, toCcy, and sz. The description adds no extra meaning, so baseline score of 3 is appropriate.

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 vague: it only contains tags '[L:READ] CAT:[资金]' and a prerequisite call. It does not explicitly state that the tool gets a convert estimate quote, relying on the tool name. No differentiation from sibling tools like okx_create_quote or okx_get_convert_currency_pair.

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?

Only mentions a prerequisite ('请先调用 agent_catalog'), but provides no guidance on when to use this tool versus alternatives. With many conversion-related siblings, the agent lacks context for selection.

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