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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds beyond that by disclosing the payload shape (name, intro, post count, address), which is valuable since there is no 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?

Three short telegraphic sentences, front-loaded with the resource and its returned fields, then the filter behavior. Efficient, though the fragment style is terse enough that a little clarity is traded for brevity.

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 annotations covering the safety profile and no output schema, the description fills the key gap by listing the returned fields and the filtering dimension. The `limit` bounding (max 20) is left entirely to the schema, which is acceptable given full schema coverage.

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%, so both `limit` and `query` are already documented with examples. The description's note that query filters name/intro is consistent with the schema but adds no syntax or format detail beyond it, so the 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 a specific resource ('관심사 방 목록', interest room list) and enumerates the returned fields (name, one-line intro, post count, address), so the agent knows exactly what this tool yields. It is clearly distinct from the siblings (debates, tests, posts, events), though it doesn't explicitly state the 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?

Usage is only implied: the final sentence indicates that `query` narrows by name/intro, hinting that this is a browse-or-search tool. There is no explicit statement of when to use this versus other listing/search tools, but the purpose is narrow enough that no conflicting sibling exists.

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