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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, but the description adds material the annotations cannot: that 签名与头像 are structurally unavailable on this path and are returned as null inside unavailable[]. It also discloses pricing and billing behavior (¥0.2/次, 仅成功计费, 失败自动退回), which directly affects whether and how an agent retries.

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?

Four short clauses, front-loaded with purpose then returns, then the null-field caveat, then usage and price. Every sentence carries information an agent needs; there is no filler or repetition of the title.

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?

There is no output schema, so the description must carry the return contract — and it does, listing the returned fields plus the one that is always null and where missing data appears. Combined with the cost model and the read-only annotations, an agent has everything needed to call it and interpret the result.

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%, so raw, _token and username are all documented in the schema, including the fact that username accepts three forms. The description adds no parameter-level meaning beyond that, so the baseline of 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 and resource (获取微信公众号资料页) and enumerates exactly what comes back (昵称、gh_username、IP 属地、原创文章数、认证主体类型、关联视频号), which effectively separates it from wechat_mp_account_articles. It stops short of naming a sibling explicitly, so the distinction has to be inferred from the returned-field list rather than being stated.

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 concrete use context that an agent can match against a task. There are no explicit when-not conditions and no named alternative such as wechat_mp_account_articles for article lists, so routing away from siblings is left to inference.

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