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

Goes well beyond the readOnly/destructive annotations by disclosing that no login is needed, that each call consumes one token ('호출마다 토큰 1소진'), and detailed idempotency-key semantics for authenticated calls. The idempotency block reads as somewhat generic boilerplate and is ambiguous against the 'no credential' framing, but it does supply genuine behavioral 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?

The purpose is front-loaded in the first sentence, but the multi-sentence idempotency passage is verbose and reads like generic text applied across many tools, and the trailing Korean token-cost note is appended without structure. Some of this content would be better trimmed or consolidated.

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 read-only list tool with one optional parameter and no output schema, the description covers purpose, auth posture, cost, idempotency behavior, and the key return identifiers. It doesn't describe the broader shape of the returned list (other fields), but the essentials an agent needs to invoke it are present.

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 coverage is 100%, so baseline is 3, but the description adds real meaning: generate and save the key before the first request, reuse only to recover a lost response with identical arguments, and use a new key for a new execution. It also clarifies the key is unavailable to anonymous calls and is distinct from a provider-specific idempotency_key.

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 (List) and resource (the Hana Bank account links this caller registered), and names the exact fields returned (account_link_id, bank_account_credential_id) that the sibling transaction history tool consumes. This lets an agent distinguish it from hana_fast_account__accounts__transaction_history__search without opening either schema.

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 says 'No credential or login required' and frames the output as the prerequisite identifiers the transaction history tool needs, giving clear context for when to call it. It stops short of an explicit when-not-to-use statement or naming a sibling alternative directly, so it falls just under a 5.

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