공식 출처 및 준비 상태 확인

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds context about the output fields, but does not disclose additional behavioral traits such as whether it returns all sources, pagination, or ordering. With annotations in place, the description provides minimal extra value but does not contradict them.

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 a single, compact sentence that front-loads the action and lists the key outputs. Every word is meaningful, with no filler or redundancy. It is appropriately sized for the tool's simplicity.

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?

Given the tool's lack of parameters, output schema, and straightforward nature, the description is mostly complete. It identifies all the data points returned, but could be slightly more explicit about the scope (e.g., 'all official sources' or 'current official sources') and whether any filtering applies. However, for a simple listing tool, this is adequate.

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 tool has zero parameters, so the baseline is 4. There is no parameter information to add, but the description clarifies what the tool returns, which indirectly helps users understand the tool's scope. Since there are no parameters, the description fully covers the semantics.

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 what the tool lists: current base date, notifications/supplements, original URL, extraction status, and chunk count. The verb '나열합니다' (list) is specific and the resource is explicit, distinguishing it from sibling tools like search_curriculum or get_curriculum_chunk, which have different purposes.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention scenarios where it should be preferred, nor any exclusions or prerequisites. The description only states what it does, leaving usage decisions to inference from the name alone.

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