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

Annotations already flag destructiveHint=true, and the description substantially enriches this by disclosing the concrete consequences: an application is filed with the NTS, a receipt record (cvaId + rcatNo) is created, and no cancel action exists. It also discloses the auth dependency and the confirm safety rule — exactly the context annotations alone cannot convey. No contradiction with 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?

Four dense sentences, each earning its place: prerequisite, action, irreversibility with concrete effects, and the preview/confirm safety rule. Critical warnings are front-loaded ahead of the workflow instructions, though the block could be structurally clearer; it remains efficient with no filler.

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 two-phase tool with 13 parameters and no output schema, the description covers the prerequisite, the correct call sequence, irreversibility, and hints at the response shape (cvaId + rcatNo). It would benefit from describing the preview response contents and the follow-up download step, but nothing needed 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 the baseline of 3 applies; all 13 parameters are documented in the schema. The description adds only flow-level context for confirm and account_link_id (the preview/confirm sequence and the same-ID-as-login requirement), which is helpful but does not add per-parameter meaning beyond the schema.

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 uses a specific verb-object pair — 'Apply for Standard Financial Statement Certificate' — that matches the Korean title and precisely identifies the resource. With many hometax__certificate__apply__* siblings (business_registration, tax_payment_record, vat_standard, etc.), naming the exact certificate type is sufficient differentiation.

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?

The description states a hard prerequisite ('REQUIRES prior hometax__session__login call with same account_link_id') and a mandatory two-phase workflow: preview first, retry with confirm=true, plus the rule 'Never set confirm=true on your own.' It does not explicitly name alternatives or when-not-to-use conditions relative to sibling apply tools, so it falls short of a full 5.

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