get_notices

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that this is a list retrieval operation, with no mention of read-only semantics, pagination, response characteristics, or relationship to the other notice endpoints. The verb '조회합니다' implies reading, but no additional behavioral context is given.

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 directly states the tool's purpose with no wasted words 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?

Although the tool has no parameters and an output schema exists, the surrounding sibling context reveals a significant gap: get_notices could plausibly overlap with get_update_notices, get_event_notices, get_cashshop_notices, and get_notice_detail. The description does not specify what type of notices are returned or when this general list should be preferred, making selection ambiguous.

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 and the schema coverage is 100% (an empty schema), so the baseline of 4 applies. There is nothing for the description to add about parameters.

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 clear action and resource: '메이플스토리 공지사항 목록을 조회합니다' (retrieves the MapleStory notice list). However, it does not distinguish this general list endpoint from the sibling tools like get_update_notices, get_event_notices, and get_cashshop_notices, so it misses sibling differentiation.

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 no guidance on when to use this tool versus alternatives. It does not mention that get_notice_detail exists for individual notices, nor does it clarify whether update/event/cashshop notices are included or should be fetched via their respective sibling tools.

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