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

The description goes beyond the annotations by stating that the action is IRREVERSIBLE, files an application with the NTS, creates a receipt record (cvaId + rcatNo), and has no cancel action. It also warns against setting confirm=true on one's own, which is critical behavioral context not present in 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 description is front-loaded with the most critical requirement (prior login), then states purpose, then irreversibility, then the confirm workflow. Each sentence adds essential operational information without fluff.

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?

With 8 parameters and no output schema, the description covers the prerequisites, the irreversible nature, and the confirm workflow, which are the most critical operational details. It does not describe the preview content or the final response structure, but the mention of cvaId and rcatNo gives a partial return hint. This is reasonably complete for a complex application tool.

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?

The input schema already describes all 8 parameters with 100% coverage. The description adds no parameter-specific meaning beyond the schema, so the baseline of 3 is appropriate.

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 clearly states that this tool applies for a National Tax Payment Certificate from Hometax, using the specific verb 'apply' and the specific resource. It distinguishes itself from sibling certificate application tools by naming the certificate type explicitly, even though it does not name a sibling.

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 provides explicit usage conditions: it requires a prior hometax__session__login call with the same account_link_id, and it prescribes a two-step workflow (preview without confirm, then retry with confirm=true). It does not, however, name alternatives or exclusion conditions, so it stops short of full when/when-not guidance.

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