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

Annotations already mark it read-only; the description adds that the response includes per-chain gas rates and halted status, which explains the dynamic/non-idempotent nature hinted by idempotentHint=false. It does not cover auth or rate limits, but for a no-param read endpoint this is useful added context.

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 sentences, front-loaded with the core purpose and followed by the per-chain return detail. Every clause earns its place; no boilerplate or repetition.

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, the description must carry return-value information; it identifies the main return categories (vault addresses per chain, gas rates, halted status) but does not describe structure or format. Given the tool's low complexity and zero parameters, this is nearly complete.

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?

There are no parameters, so per the rubric the baseline is 4; schema coverage is 100% and there is nothing for the description to compensate for. No additional parameter meaning is needed.

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?

States a specific verb ('Returns') and resource ('vault addresses' / 'inbound address') and ties it to the concrete use case of depositing assets into THORChain. The per-chain scope and inclusion of gas rates/halted status distinguishes it from generic vault-listing siblings.

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 phrase 'for depositing assets into THORChain' implies the usage context, but the description does not explicitly state when to choose this over siblings like get_vault or list_asgard_vaults, nor does it list prerequisites or exclusions. Usage is only implied.

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