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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds genuinely new behavior: an account-connection prerequisite, idempotency semantics, and a per-call cost ('호출마다 토큰 1소진'). The odd phrase 'not available to anonymous taste calls' is unclear boilerplate that slightly muddies the otherwise useful disclosure.

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?

Purpose and returned fields are front-loaded, but roughly half the text is a generic idempotency-key tutorial with internal redundancy ('Without it, calling again remains a new request') for what is a simple two-parameter read. The trailing Korean token-cost note and the provider-specific idempotency_key aside add noise relative to this tool's scope.

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, two-optional-parameter tool with full schema coverage and annotations, everything needed to call it correctly is present: what it returns, the account-connection precondition, key handling, and cost. No output schema exists, and the description compensates by naming the returned fields.

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 meaning beyond the schema for request_idempotency_key (generate before the first request, reuse only for that request, new key for new execution) — the schema itself just defers to the description. account_link_id's auto-resolution behavior is only in the schema, not the description.

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 ('Returns the Naver Search Ad account's business money (bizmoney) balance') and even enumerates the returned fields (budgetLock, refundLock). This clearly distinguishes it from the sibling naver_searchad read tools (adgroups, ads, campaigns, keywords, performance), which all return data of a different kind.

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?

Gives a concrete prerequisite ('Connect the Naver Search Ad account first') and rules for the idempotency key (new key per execution, reuse only for recovery of a lost response). It does not name when to choose this over alternatives or when not to call it, so it falls short of the explicit when/when-not routing of a 5.

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