okx_get_deposit_address

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

No annotations are provided, so the description must carry the burden. '[L:READ]' hints at a read-only operation, but there is no disclosure of permissions, rate limits, or whether it returns addresses for all chains. The description is minimal and does not add substantial behavioral context beyond the read hint.

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 one line, very concise, but includes fragmented tags and Chinese text. It is not well-structured for an English-speaking agent, but it is not verbose. Conciseness is acceptable but lacks clarity.

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 a simple tool with one parameter and no output schema, the description is incomplete. It does not mention that the deposit address might depend on the network or that it returns a single address. The sibling list includes many related tools, but the description fails to provide sufficient context for an agent to confidently invoke it.

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 schema has 1 required parameter 'ccy' with a description in Chinese stating 'currency, e.g., USDT, BTC, ETH'. Schema coverage is 100%, so the description adds no extra meaning beyond the schema. 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 name 'okx_get_deposit_address' indicates it retrieves a deposit address. The description adds '[L:READ]' and category '[资金]' but does not explicitly state that the tool returns the address for a given currency. The purpose is moderately clear but lacks specificity about the output format or 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 description instructs to call 'agent_catalog' first, implying a prerequisite, but provides no guidance on when to use this tool over alternatives like 'okx_get_deposit_history' or 'okx_get_deposit_lightning'. No exclusions or context for selection are given.

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