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

Annotations declare destructiveHint=true, and the description goes well beyond them: the action is irreversible, cannot be cancelled, persists in the institution's records, the rrno is never echoed back, and each call consumes one token. It also discloses the preview masking behavior (names plus last 4 digits), which no annotation covers.

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 prerequisite is front-loaded and every sentence carries operative information; nothing is filler. It is a single dense block, though, and the token-cost note trails in Korean after the safety rules, which slightly weakens scannability.

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 destructive, no-output-schema mutation tool, the description covers everything needed: session prerequisite, ordering against the issue tool, batch limits, required per-subscriber PII, preview/confirm protocol, and irreversibility. Nothing an agent needs in order to call it safely 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 description coverage is 100%, so confirm, subscribers, member_name, rrno and account_link_id are already fully documented in the schema. The description reinforces the confirm workflow and the 13-digit rrno rule but adds no syntax or format detail the schema lacks, so the baseline of 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 (send/apply) plus the exact resource (NPS membership certificate application, form EB0301) and the batch bounds (1 to 100 subscribers). It also positions itself relative to the sibling issue tool, so an agent can tell apply from issue 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?

Explicit prerequisites: a prior nps_edi__auth__npki_session__login with the same account_link_id, and the ordering rule that application must precede issuing because the issue screen lists subscribers only under a received application document number. It also prescribes the two-step call sequence (preview, then confirm) and forbids self-approving.

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