queryDepositAddress

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

Annotations already declare readOnlyHint and openWorldHint. The description adds meaningful behavioral detail beyond those annotations by enumerating error conditions (banned, custody, UAE-restricted) and permission restrictions (main UID only, no sub-accounts). This gives the agent useful expectations without repeating annotation content.

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 compact and front-loaded, beginning with a one-entence purpose statement followed by tight bullet points. Every sentence contributes a non-obvious constraint or behavior, with no redundancy or filler.

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?

Access constraints are well covered, but the tool has no output schema and the description does not describe the return value, response shape, or how coin/chainType influence the result. An agent cannot fully anticipate what the tool returns or how to configure the optional chainType parameter.

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 descriptions coverage is 0%, and the description does not explain either parameter. The 'coin' parameter is only indirectly implied by 'UAE-restricted coins,' and 'chainType' is not addressed at all. The agent gets no help understanding valid values, formats, or how the parameters affect the result.

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 a specific verb and resource: 'Query the deposit address information for the master account.' It also distinguishes itself from sibling tools like querySubMemberDepositAddress by explicitly noting that sub-accounts are not allowed, making its scope and boundary immediately clear.

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 provides clear eligibility context: only main UID API keys may call, sub-accounts cannot, and certain user/coin types will error. However, it does not explicitly name an alternative tool such as querySubMemberDepositAddress for sub-account use, so routing to alternatives is implied rather than stated.

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