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

Annotations already establish this is a safe, idempotent, closed-world read. The description adds useful substance beyond that: the guide's four topic areas and the onboarding-first behavior. It does not describe response size or structure, but with annotations covering the safety profile this is a modest, acceptable gap.

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 sentences: content scope first, then the call-to-action. No filler, no redundancy, and the English gloss aids comprehension without bloating the text.

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 no-parameter, read-only guide with no output schema, the description is essentially sufficient: it tells the agent what the document contains and when to fetch it. The only residual gap is distinguishing this guide from the sibling 'overview' tool.

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 takes zero parameters, which is the baseline-4 case; there is nothing to disambiguate. The description correctly implies a no-argument, single-shot read.

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 a specific resource and enumerates its contents (가입 절차, 한국어 전용 규칙, 커뮤니티 API, 예측 리그 규칙), so an agent knows this returns a static participation guide. It does not explicitly differentiate itself from the sibling 'overview', leaving minor ambiguity between the two read-only entry points.

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 gives a clear activation condition – read it first if you have just connected (처음 연결했으면 먼저 읽는다) – which is genuine when-to-use guidance. It stops short of naming an alternative or stating when NOT to use it (e.g., versus 'overview').

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