queryDepositAddress

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

With no annotations, the description fully discloses behavioral traits: authentication requirements, exclusion of sub-accounts, and error conditions for banned/custody/UAE users. It does not describe the return format, but the query nature implies the address is returned.

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 efficient: one concise sentence followed by four informative bullet points. No redundant information; every sentence adds 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?

Given the lack of parameter documentation and output schema, the description is adequate but not complete. It covers purpose and constraints well but misses parameter semantics, which is a notable gap for a 2-parameter tool.

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 0% and the description adds no explanation for the 'coin' or 'chainType' parameters. While 'coin' is somewhat inferred, 'chainType' is not defined at all, leaving the agent unclear about possible values or optionality implications.

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?

Description clearly states the tool queries deposit address information for the master account. It specifies the resource and action ('Query the deposit address information') and distinguishes from sibling 'querySubMemberDepositAddress' by explicitly targeting the master account, not sub-accounts.

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?

Provides explicit constraints on who can call (main UID API key) and who cannot (sub-accounts, banned/custody/UAE-restricted users). While it does not name an alternative tool, the sibling list includes 'querySubMemberDepositAddress' for sub-accounts, making the context clear.

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