wechat_scraper

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

With no annotations provided, the description must fully disclose behavioral traits. It only states the core fetch-and-convert action without details on error handling, network requirements, anti-scraping issues, or the exact output format. This is a significant gap for a scraper tool.

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 one concise sentence that is front-loaded and contains no redundant information. Every word contributes meaning, making it an efficient and well-structured statement.

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 tool is a scraper with one parameter and no output schema, yet the description does not explicitly explain what the return value is (e.g., whether Markdown is returned as a string, file, or in another format). It also lacks information about error behavior or limitations, leaving the agent under-informed for a non-trivial operation.

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 already fully documents the single 'url' parameter with a clear description, achieving 100% schema coverage. The tool description adds no additional context beyond what the schema provides, so a baseline score of 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?

The description clearly states the tool's function: fetching WeChat official account articles and converting them to Markdown. The verb '抓取' specifies the action and resource explicitly, and it distinguishes itself from the sibling tool md2card_api, which likely performs the reverse operation.

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 provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites or edge cases. While the sibling tool exists, no differentiation is offered, leaving the agent without context for selecting this tool over others.

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