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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: results are ordered most-recent-first, the unfiltered call returns aggregates rather than records, and there is a usage/copyright restriction requiring source-URL citation. Return format and pagination limits are left implicit.

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 with the core purpose, then the no-filter case, then the fetch hand-off, then the legal note. Sentences earn their place, though the copyright/citation sentence is somewhat tangential to invoking the tool.

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 no output schema, the description usefully explains what comes back (a recent-ordered list, or classification+counts when unfiltered) and how to get full text. It omits return shape details like pagination or the fields of each list item, which keeps it just short of complete.

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 every parameter including the default limit of 20 is already documented in the schema. The description restates the filter dimensions but adds no syntax, matching rules, or format guidance beyond what the schema provides.

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 states a specific verb (반환/목록) plus the exact resource (회계위키 수록 금감원·한공회 감리지적사례) and the filterable dimensions (계정·위반유형·기관·연도·키워드). It also distinguishes behavior from a sibling by stating that passing a list id to fetch yields the full case text, so an agent can tell list vs. detail apart.

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 clearly explains the no-filter branch (returns classification and counts) and routes the agent to fetch for full text via the id. It stops short of explicitly saying when NOT to use this tool or naming other alternatives among the many sibling search/list tools.

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