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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds value by disclosing the return granularity ("a summary of each account (address, name)") and pointing to where richer fields live, though it says nothing about behavior on an unknown wallet address (empty result vs error).

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?

Three short sentences, front-loaded with the core action, followed by return shape and the routing hint. No filler or restated name/title.

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 annotations covering read-only safety, an output schema defining return values, and full schema parameter coverage, the description supplies exactly the missing piece: the escalation path to read_account_info. Nothing an agent needs to call this correctly is absent.

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%, with wallet_address and chain_id both documented including the enumerated chain ID values, so the schema carries the parameter burden. The description only reinforces the ownership semantics of wallet_address and adds no format or default information 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 and resource ("List all Arcadia accounts owned by a wallet address") with an explicit ownership scope, which separates it from sibling listing tools like read_wallet_balances. It also names the companion detail tool, so the boundary between this and read_account_info is unambiguous.

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?

Explicitly routes the agent: use this for the account list, then call read_account_info with a specific account_address for health factor, collateral, and debt. The when-to-use-this vs when-to-use-the-alternative distinction is stated rather than inferred.

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