room_members

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

无 annotations，描述承担行为说明职责。它说明了工具是只读查询、返回成员列表并解释 chat_id 缺省行为，但未披露任何可能的权限要求、失败情形或数据即时性等行为特征。

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?

两句话完整说明用途、返回值与缺省行为，信息密度高且无冗余，属于精炼的合格描述。

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?

对单参数只读列表工具，描述已说明返回字段、缺省行为和使用场景；缺少输出结构样例或错误条件，但整体足以让 agent 正确调用。

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?

参数仅有 chat_id，schema 已包含描述；描述额外说明了省略 chat_id 时的默认行为（取最近对话房间），为参数语义增加了超出 schema 的价值。

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?

描述使用明确动词「获取」与资源「指定 Matrix 房间（群聊）的在场成员列表」，并具体说明返回 user_id 与 display_name，足以与 siblings 如 list_rooms、room_info 区分。

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?

描述说明 chat_id 省略时取最近转发进来的房间，提供了明确的使用上下文；但未明确说明何时不使用本工具（例如需要房间详情时用 room_info），因此未达满分。

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