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

Annotations already establish read-only, non-destructive behavior. The description adds the auth dependency and same-account-link requirement, which is useful, but it says nothing about pagination, result shape, or NTS-side behavior/limits; with annotations covering safety, a 3 is appropriate.

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?

Short and front-loaded with the most important prerequisite, with no filler. The parameter notes are terse but somewhat redundant with the schema; overall it is efficient, though slightly fragmentary.

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?

Together with a fully-described schema and read-only annotations, the description provides enough to call the tool safely: login prerequisite, required parameters, and formats. Missing output/pagination semantics and the sibling distinction are notable gaps, but they are not blocking for a basic search invocation.

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 schema documents all six parameters with 100% coverage, including the full enum mapping for mate_knd_cd. The description just restates the document-type and YYYYMM formats, adding no meaning beyond the schema, so the baseline 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?

Identifies a concrete operation: search tax payment statement, aligned with the title '납부 내역 조회'. However, it does not contrast with the sibling search_submit_history tool, so the agent cannot distinguish this search variant from related siblings based on the description alone.

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?

Clearly states the critical precondition: a prior hometax__session__login call with the same account_link_id. It gives no when-to-use/when-not-to-use guidance or alternatives, so selection among the many hometax search tools is left implicit.

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