Reads up to 10 WeChat article URLs at once and converts each into Markdown, enabling batch summaries or analysis of provided links.
Read up to 10 WeChat articles at once and return each as Markdown. Use when the user provides a batch of URLs (e.g. from a list they want summarized).
| Name | Required | Description | Default |
|---|---|---|---|
| urls | Yes | List of WeChat article URLs (each must be mp.weixin.qq.com) |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral burden. It discloses that this is a read operation and that results come back as Markdown with a max of 10 articles, but it omits per-URL failure behavior, whether one bad URL fails the batch, and any auth or rate-limit constraints.
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?
Two tight sentences, zero waste, with the core capability front-loaded before the usage condition.
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 one-parameter read tool with no output schema, the description covers purpose, batch limit, output format, and usage context. It could be more complete about partial failures in a batch, but it is otherwise sufficient.
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 100%, and the schema already documents the array, min/max items, and required mp.weixin.qq.com domain. The description adds only the batch-size framing, so baseline 3 is appropriate.
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?
States a specific verb and resource ("Read ... WeChat articles") plus the batch limit and Markdown return format. The word "multiple" and "up to 10 ... at once" implicitly distinguishes it from the singleton sibling read_wechat_article, though it does not name that sibling explicitly.
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?
Gives a clear triggering context: "Use when the user provides a batch of URLs (e.g. from a list they want summarized)." It does not explicitly state when to use the sibling single-article tool instead, but the batch condition is unambiguous.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.