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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the write/irreversible profile is partially covered. The description adds real context beyond that: the application is filed with the NTS first, a receipt record (cvaId + rcatNo) is created, there is no cancel action, files are retained 7 days with 15-minute download links, and each call costs one token. However, much of the remaining text (anonymous recovery_receipt handling) describes xdata__job__result behavior rather than this tool's own traits.

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?

Front-loaded well: the session prerequisite and the one-step apply+download purpose come before any detail, and the critical confirm-safety rule is prominent. It runs long, though, with a multi-sentence anonymous recovery_receipt tutorial that is boilerplate for a tool that requires an authenticated session.

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?

No output schema exists, so the description carries the return-value burden and does it: artifacts[] entries, unchanged PDF, download_url valid 15 minutes, 7-day retention, cvaId + rcatNo receipt, and job_id for requesting fresh links. An agent has everything needed to invoke and then follow up correctly.

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% and both parameters (confirm, account_link_id) are already well documented in the schema, so the baseline is 3. The description adds one genuine constraint not in the schema — account_link_id must match the one used at session login — but otherwise repeats the preview/confirm flow already stated in the confirm parameter 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?

Names a specific verb pair (apply + download) and resource (납세증명서 / national tax payment certificate), and states the defaults-fixed scope. It explicitly distinguishes itself from hometax.certificate.apply.national_tax_payment (options) and the template variant, so an agent can pick it without opening sibling schemas.

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 prerequisites (prior hometax__session__login with the same account_link_id) and an explicit call sequence: call without confirm to get a preview, show the user, retry with confirm=true, never self-approve. It also names the alternative tool for the case where issuance options must be configured.

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