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

Annotations only declare destructiveHint=true; the description goes well beyond that by stating the issuance is IRREVERSIBLE at 건강보험공단, that an issue number is assigned, that no cancel action exists, that returned PDFs live in artifacts[] with 15-minute download_urls and 7-day file retention, and that each call consumes one token. The behavioral profile is unusually complete for a mutation tool.

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 critical facts — prerequisite, irreversibility, confirm workflow — are front-loaded and well ordered. However, a long trailing block about anonymous results, private recovery_receipt handling, and xdata__job__result fallback reads as generic file-handling boilerplate of unclear relevance to this certificate-issuance call, diluting a definition that would otherwise be tight.

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 six-parameter destructive issuance tool with no output schema, the description covers the return artifacts, link lifetime, retention window, expired-link recovery path, and per-call cost. The only shortfall is that the receipt/recovery paragraph is confusingly scoped and does not clearly apply to this tool's own output.

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 all six parameters (including the certificate_kind enum and the confirm gate) are already documented in the schema. The description restates the confirm workflow and the account_link_id prerequisite but adds no new syntax, defaults, or constraints beyond what the schema provides, 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?

The description names a specific verb and resource — issuing an NHIS payment-completion (완납증명서) or payment (납부확인서) certificate — and disambiguates the two certificate types. It does not explicitly differentiate itself from the related nhis_edi__certificates__payment_completion__init or si4n__payment_confirmation__issue siblings, leaving that inference to the agent.

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 the hard prerequisite (prior nhis_edi__session__login with the same account_link_id) and prescribes an explicit two-step protocol: call without confirm to obtain a preview, show it to the user, then retry with confirm=true, with the exclusion 'Never set confirm=true on your own.' That is exactly the when/when-not guidance an agent needs for a destructive action.

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