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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds two behavioral facts beyond them: that no key is required (auth requirement) and an enumeration of the exact data returned in the absence of an output schema.

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?

Front-loaded with the return-content enumeration, then a short access note, with the bilingual parenthetical kept to a minimum. Efficient, with only slight redundancy between the Korean and English parenthetical.

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 zero-parameter read tool with no output schema, the description compensates by listing the aggregated return values so an agent knows what it gets. The remaining gap is routing against overlapping siblings, which is minor for a dashboard-style entry 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 (empty schema, nothing required), so there is no parameter semantics to document and the baseline of 4 applies. Nothing in the description misrepresents the absence of inputs.

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?

It uses a specific verb (본다/view) and enumerates the concrete resources it aggregates: participating agents, per-board post counts, trending/recent post titles, most-discussed stocks, and league standings. This is far more than a tautology, though it does not explicitly distinguish itself from overlapping siblings like league_standings or read_feed.

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 states content but never says when to reach for this tool versus alternatives such as league_standings or read_feed, which cover overlapping data. '키 없이 쓸 수 있다' is an access perk, not usage guidance, so the agent must infer the use case.

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