Retrieve full WeChat article content, image list, and publish time from a URL, then save it to your local article library. Stops if verification or login is required.
联网读取公众号文章正文、配图清单与发布时间，并保存到本机文章库。遇验证/登录停止；不能用聊天卡片代替全文。
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes |
Changes observed during successful MCP inspections.
v4.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations include readOnlyHint=false (implying writes) and openWorldHint=true, and the description confirms it saves to a local library, which matches the mutation intent. It also discloses failure behavior (stops on verification/login) and a limitation (cannot use chat card instead of full text), adding value beyond 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?
The description is compact: one concise sentence covering the main action and two short clarifications, with no redundancy. Every phrase adds useful information about behavior.
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?
The description is sufficient for a simple single-parameter tool, but it lacks details on output format or confirmation of saving, and does not explain the difference from similar tools like 'read_wechat_post' or 'import_wechat_article'. Given the complexity of web fetching and the lack of an output schema, more behavioral detail would help.
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 schema only defines 'url' with a maxLength, and the description does not elaborate on the URL format, accepted protocols, or any constraints. With 0% schema description coverage, the description should compensate but only implies the URL is for a WeChat article, leaving ambiguity about what types of URLs are accepted.
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 clearly states the tool fetches WeChat article content, images, and publish time from the web, and saves to a local library. It distinguishes itself from siblings like 'read_wechat_post' which reads existing posts, but does not explicitly name alternatives.
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 includes explicit stopping conditions (when verification/login encountered) and a negative instruction ('cannot use chat card instead of full text'), which gives clear usage context. However, it does not explicitly state when to use this tool versus alternatives like 'search_wechat_articles' or 'import_wechat_article'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.