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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds real behavioral value by disclosing the return fields (title, room, posted date, excerpt, address) and the special behavior for stock rooms (official schedule included), but says nothing about ordering, recency default, or truncation.

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?

Two short, dense sentences with no filler, and the resource scope is front-loaded. The telegraphic style borders on cryptic (e.g. bare field list '제목·방·올린 날·발췌·주소'), but nothing is wasted.

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 enumerates returned fields, which compensates somewhat. However, for a 4-parameter search tool with a near-duplicate sibling, the absence of any routing guidance or result-ordering behavior leaves a meaningful gap.

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% and all four parameters carry descriptions (room slug, limit 1-20, keyword, upcoming_only 30-day window), so the schema carries the load. The description only hints at room-scoping via '방별' and adds no semantics beyond the schema; 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?

The description names the resource (per-room event/discount posts tagged [행사]·[혜택]) and lists the returned fields, so the agent can guess it retrieves event news. But it contains no verb (search/list/fetch) and never explicitly contrasts with the sibling search_posts, which also searches posts — the only differentiator is the tag hint, which the agent must infer.

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?

There is no explicit when-to-use statement and no named alternative, despite a close sibling (search_posts) existing. The agent must infer from the tag bracket that this tool is for event/benefit posts only; '주식 방은 공식 일정표도 함께' adds a special case but not general usage guidance.

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