kraken_get_deposit_addresses

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

With no annotations, the description must disclose behavioral traits, but it does not mention that setting 'new' to true generates a new address with potential side effects, nor does it clarify read-only status. The 'Get' phrasing is misleading if 'new' is used, as it's more than a simple retrieval.

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 a single, efficient sentence that immediately states the action and resource, with no filler or redundancy. It is well-structured and front-loaded.

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?

While an output schema exists, the description fails to convey important context such as the dependency on deposit methods, the effect of the 'new' flag, or any operational prerequisites. The tool's generative capability is omitted, making the description incomplete for effective use.

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 input schema already provides complete descriptions for all three parameters (asset, method, new) at 100% coverage. The tool description adds no additional semantic value beyond referencing 'selected method', so it meets the baseline without enhancing understanding.

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 uses the verb 'Get' and identifies the resource as 'deposit addresses for an asset', which is specific and distinguishable from sibling tools like 'get_deposit_methods' and 'get_deposit_status'. However, it does not explicitly mention the 'new' parameter behavior or differentiate between retrieving existing vs generating new addresses, so it's not fully distinct.

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 no context on when to use this tool versus alternatives, such as first calling 'kraken_get_deposit_methods' to obtain a method ID, or when generating a new address is appropriate. No exclusions or prerequisites are stated, leaving the agent without guidance.

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