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

The annotations declare readOnlyHint=false, and the description explains why: each call creates an XBOSS task, stores the result, and is explicitly '순수 읽기 전용이 아닙니다'. It also discloses a per-call cost (토큰 1소진) and details how an optional idempotency key behaves on retries. The English block is partly boilerplate and mentions 'anonymous taste calls', which is confusing noise, but the side-effect and quota disclosure is genuine value beyond the annotations.

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 sentence is front-loaded and clear, but the middle section is a long mixed Korean/English block that repeats the idempotency rule three different ways and includes provider-generic boilerplate about '기관 데이터 변경'. It is readable but noticeably padded for a two-parameter validation call.

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 two-parameter validation tool with no output schema, the description covers the source, the required per-item fields, the cost, the non-read-only side effect, and the idempotency contract. The main gap is return-shape expectation (no output schema exists, so the agent cannot know what a match/mismatch response looks like), but otherwise nothing needed to call it correctly is missing.

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 the per-field meanings of b_no, start_dt, p_nm and the optional fields are already documented. The description goes beyond that by carrying the actual contract for request_idempotency_key, which the schema defers to it ('see the tool description'), including reuse-only-for-recovery and new-key-per-execution rules. That is the one parameter whose semantics the schema alone would not convey.

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?

The description names a specific verb and resource: it verifies whether business-registration information matches, and it names the upstream source (NTS via data.go.kr 15081808). That is concrete enough that an agent knows exactly what the call answers. What it does not do is explicitly separate the tool from its closest sibling, opendata__nts__status, so the agent has to infer the difference from the names alone.

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?

It states that the tool can be used '별도 연동 없이' (with no separate integration), which is a real usage precondition. Beyond that, it gives no guidance on when to prefer this over a status lookup or when not to call it, and the idempotency-key paragraph describes mechanics rather than tool selection. Usage is implied by the purpose, not stated as a decision rule.

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