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

Annotations already declare readOnlyHint=true and idempotentHint=false, so the safety profile is covered. The description adds one behavioral nuance, that the public key is returned only 'if available', which is useful. It does not address return format, error behavior, or why a read would be non-idempotent.

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?

A single efficient sentence with the resource and return contents front-loaded and zero filler. Slightly terse given it could carry more context, but nothing is wasted.

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?

No output schema exists, so the description partly compensates by naming the returned fields (account number, sequence, public key). For a simple single-param read tool this is nearly complete, with only the conditional 'if available' nuance left underspecified.

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 100%, so the single 'address' parameter and its format hint (thor1...) are already documented. The description repeats 'THORChain address' without adding format, validation, or edge-case detail beyond the schema. Baseline 3 applies.

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+resource ('Returns account information for a THORChain address') and enumerates the key return fields (account number, sequence/nonce, public key). This distinguishes it in content from siblings like get_cosmos_balances or get_cosmos_tx, though it does not name any sibling explicitly.

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 explicit when-to-use, when-not-to-use, or alternative routing is given. The usage is implied by the purpose (fetch on-chain account state for a given address), but an agent must infer when this is preferable to get_cosmos_balances, get_trade_account, or get_thorname_owner.

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