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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description adds nothing beyond that. It doesn't describe pagination behavior, ordering, or any side effects. With annotations covering the safety profile, the description's minimal addition is acceptable but not enriching.

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?

A single sentence that is direct and free of fluff. The purpose is front-loaded and nothing is redundant.

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 read-only list tool with an output schema and fully documented parameters, the description is sufficient. It covers the core action. Slight gap: it doesn't mention that the page_token is used for continued pagination, but that's already in the schema. Overall, the combination of schema and description is complete enough for an agent to call correctly.

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%, so both parameters (account_id and page_token) are fully documented in the schema. The description doesn't add any semantic detail beyond the schema, such as the meaning of the account_id format or the pagination rule, which are already in the schema. 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?

The description clearly states the verb (获取/get) and the resource (文章列表/article list) with a specific scope (按公众号账号 ID/by account ID). It distinguishes from siblings like wechat_get_mp_account_info_by_account_id which retrieves account info, not articles.

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 implies usage: when you have an account ID and need its articles. However, it doesn't explicitly state when to prefer this over siblings or mention any exclusions (e.g., if you have a URL, use wechat_get_mp_article_detail_by_url). It provides no context about the pagination flow beyond what the schema explains.

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