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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds meaningful output-side behavior: prefer content_text for body reading, image_urls for images, content_html preserves original structure, and account.account_id can feed account info/published-list queries — context not derivable from annotations alone.

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?

Front-loaded with the trigger condition, then output-field guidance, then sibling routing — each sentence earns its place. Slightly dense multi-clause packing, but no filler.

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?

An output schema exists, so return shape need not be explained, but the description usefully points at the key fields and cross-tool reuse of account.account_id. For a one-parameter read tool this is essentially complete; only the absence of explicit sibling names keeps it below 5.

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 coverage is 100% and the single url parameter is fully documented in the schema, including that share text containing a link is acceptable. The description restates the 'link or share text' acceptance but adds no format or edge-case detail beyond the schema, so baseline 3 applies.

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+resource: retrieving details, body text, and ordered images for a WeChat Official Account article or image-post from a URL. It explicitly narrows scope to '普通文章或贴图' (normal articles or image posts), which distinguishes it from the video, comment, and stats siblings.

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?

Sets a clear precondition — '已有微信公众号文章链接或包含链接的分享文案时' (when you already have the link or share text containing it) — and explicitly routes stats/comments to other tools ('统计或评论请使用对应工具'). It does not name the specific sibling tools, so the routing requires the agent to map to the named siblings itself.

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