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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered; the description goes well beyond by disclosing there is no pagination or total/offset, no snippet because there is no query, and that date sorting means retroactively registered old documents never surface as new. The response object shape is also spelled out field-by-field, which is valuable since no output schema exists.

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?

Bracketed headers ([Purpose], [Usage], [Response], [Rules]) make it front-loaded and scannable, and every line carries information. It is somewhat longer than a two-parameter tool strictly requires, but no sentence is 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 simple, zero-required-parameter read tool with no output schema, the definition covers ordering, filtering, response fields, the absence of pagination, and the key/label asymmetry. Nothing an agent needs to call it correctly 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 coverage is 100% with an enum on board, so the baseline would be 3, but the description adds a genuinely non-obvious constraint: board accepts the English key while the response returns the Korean label, and the response board value must never be fed back as a parameter. That asymmetry is exactly the kind of semantic detail the schema cannot express.

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 first sentence states a specific verb (반환합니다/list) and resource (최신 문서 목록) plus ordering (게시일 내림차순), and the Usage section implicitly separates it from search_documents. An agent can tell this is a query-less browse tool, distinct from get_document and search_documents, without opening the schema.

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?

Three concrete user-utterance-to-parameter mappings (no args → limit=20; sanction_case + limit=10; fsc_press) give the agent worked examples, and the closing rule explicitly routes period/topic narrowing or larger volumes to search_documents. Both when-to-use and the exclusion are stated.

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