Batch view recent message summaries from candidates filtered by job, label, or chat list to quickly assess recruiter conversations and identify active leads.
招聘者模式：批量查看候选人最近消息摘要 [可用性: 可用性: roles=recruiter; candidate_platforms=-; recruiter_platforms=zhipin-recruiter]
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | 沟通列表页码 | |
| job_id | No | 按职位筛选 | |
| label_id | No | 标签筛选（0=全部, 1=新招呼, 2=沟通中） | |
| friend_ids | No | 候选人会话 friend_id 列表；不传时从 hr chat 页获取当前页候选人 |
Changes observed during successful MCP inspections.
v1.19.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
没有提供任何标注（annotations），因此描述必须承担行为透明度的全部责任。但描述仅说明功能，未提及任何行为特征，例如是否只返回摘要而不包含完整消息、分页行为、是否需要特定权限（虽然可用性提示提到角色，但未详细说明）、是否只返回当前页面的候选人等。缺少对操作影响和返回内容的披露。
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?
描述简短，但存在一个明显的重复错误：“[可用性: 可用性: ...]”，这破坏了专业性。内容上比较精炼，但结构简单，没有分点或结构化呈现。考虑到错误，给3分。
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?
工具涉及4个参数，但没有输出模式，且描述未说明返回内容（如摘要的格式或字段）。对于批量摘要工具，代理需要知道返回什么，但描述缺失。此外，没有说明不传 friend_ids 时如何获取候选人，虽然模式中有提到，但描述没有强化。整体信息不完整，代理可能难以正确使用。
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?
参数模式提供了100%的覆盖，每个参数都有详细描述（如 page 是沟通列表页码，job_id 按职位筛选等）。描述本身未增加额外语义，但依赖模式已足够。基线为3，合理。
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?
描述明确说明了工具的功能：批量查看候选人最近消息摘要，并指明了招聘者模式。这足以让代理理解工具的基本用途，并能与兄弟工具如 boss_hr_chat、boss_chatmsg 等区分开。但描述中没有提及任何区分性的细节，比如与单个聊天查看的区别，因此未达到5分。
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?
描述没有提供任何关于何时使用此工具、何时使用替代工具（如 boss_hr_chat 或 boss_chatmsg）的指导。也没有提及使用前提或限制条件（除了提示中的角色限制）。代理无法确定该工具是用于批量获取摘要还是用于具体场景，缺乏使用上下文。
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.