Fetch basic profile details for multiple WeChat users at once by submitting a list of openids. Streamline audience data retrieval for analysis and targeted communication.
批量获取用户基本信息。
| Name | Required | Description | Default |
|---|---|---|---|
| openid_list | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds no behavioral context beyond that, such as maximum batch size, rate limits, handling of invalid openids, or ordering of results. It simply restates the operation.
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?
A single, concise sentence with no filler or redundancy. The core action and resource are front-loaded, making it easy to scan.
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 simple read-only batch operation with an output schema and safety annotations, the description is serviceable. However, it omits operational details like batch size caps, behavior for unknown openids, and explicit relationship to get_user_info, leaving an agent without guarantees needed for robust invocation.
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 description coverage is 0%, so the description must compensate. It clarifies that openid_list contains user identifiers by referring to 用户基本信息, but it does not explain what an openid is, list length limits, or behavior for empty or invalid entries. Adds minimal meaning over the 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?
The description '批量获取用户基本信息' states a specific verb (batch get) and resource (user basic information). The batch modifier clearly distinguishes it from sibling get_user_info, so an agent can identify this as the multi-user variant.
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?
No explicit guidance is provided about when to use this tool versus get_user_info. The batch prefix implies use for multiple openids, but the description does not explicitly name the single-user alternative or state when-not-to-use. Guidance is only implicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.