get_deposit_methods

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

No annotations exist, and the description fails to disclose behavioral traits such as read-only nature, required permissions, rate limits, or side effects. For a listing operation, being read-only is likely, but it is not stated.

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 exceptionally short (one sentence), which is concise but lacking in necessary details. It earns its place by being direct, but could include more information without losing conciseness.

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?

With no output schema and 0% parameter descriptions, the description is insufficient for an agent to fully understand tool behavior. It lacks details on response structure, error handling, or data format.

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 description coverage is 0%, and the description does not explain the parameters 'asset' or 'aclass'. The agent cannot infer what values to provide or the purpose of 'aclass'.

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 'List available deposit methods for an asset,' which includes a specific verb ('list'), a distinct resource ('deposit methods'), and context ('for an asset'). It differentiates well from siblings like 'get_deposit_addresses' and 'get_withdrawal_methods'.

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?

No guidance is provided on when to use this tool versus alternatives like 'get_deposit_addresses' or 'get_withdrawal_methods'. The description does not specify prerequisites or scenarios.

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