Get Deposit Addresses

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

It discloses the required environment variables (POLONIEX_API_KEY/POLONIEX_API_SECRET) and implies a read-only operation via 'fetch', adding value beyond the schema. It doesn't mention rate limits or response format.

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?

Two concise sentences, front-loaded with the action, no 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?

For a single-optional-parameter getter, this description covers purpose, usage, and auth. The lack of output schema is acceptable given the simple resource.

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 already fully documents the `currency` parameter with the same omit/pass behavior, so the description adds no new meaning beyond restating the schema description.

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 states the specific action ('Fetch deposit addresses') and the account scope, clearly distinguishing it from sibling getter tools like get_balances or get_wallet_activity.

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?

It provides clear instructions for the optional parameter ('Omit currency for all currencies, or pass one for a single currency') and auth prerequisites, but doesn't explicitly contrast with alternative tools.

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