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

The annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true), so the description only needs to add operational context — but it adds none. It says nothing about result ordering, page size, whether an empty list is possible, or how the pagination chain terminates, despite page_token being an interface concept.

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?

One short sentence with no filler and the resource is front-loaded. It is efficient but so terse that the conciseness shades into under-specification.

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 values needn't be explained, and the schema fully specifies the parameters. Still, for a paginated list tool with an open-world hint, the description leaves the pagination flow and result scope entirely to the schema.

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 input schema already documents both parameters at 100% coverage, including the gh_ example format for account_id and the rule of passing the entire next_page_token back unchanged. The description adds no meaning beyond the schema, so the baseline of 3 for high coverage 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?

The description states a specific verb and resource (get article list) keyed on an official-account ID, which is concrete enough to act on. It does not explicitly contrast with wechat_search_mp_articles or wechat_get_mp_account_image_posts_by_account_id, so the agent must infer the distinction from the name alone.

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?

There is no guidance about when to use this tool rather than the sibling search_mp_articles or the image-posts variant. Nothing says whether the list is chronological, capped, or requires an already-resolved account_id.

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