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

Annotations only cover the safety profile (readOnly, idempotent, openWorld), so the description carries real weight here: it discloses latency (6~18s), recommends a client timeout above 30s, states pricing (¥0.2/次), and clarifies billing only occurs on success with automatic refund on failure. Those are operational facts an agent cannot get from annotations or schema.

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 front-loaded with the purpose and recommended variant, then the returned fields, then usage, then operational caveats. It is dense but every clause carries information; the pricing/slow-response notes are slightly appended-looking but still earn their place.

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?

No output schema exists, yet the description enumerates the returned fields explicitly, so the agent knows what comes back. Combined with latency, timeout and billing guidance, it is complete enough to invoke correctly without opening 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?

Schema coverage is 100% and each of the four parameters already has its own description, including the h5/raw tradeoffs and the _token alternative auth. The description adds no param-level semantics 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?

The description states a specific verb+resource (获取微信公众号文章详情) and enumerates the exact returned fields (标题、作者、公众号昵称与 username、正文 HTML、封面图、发布时间、合集信息、评论 id). It also marks the H5 variant as recommended, distinguishing it from the faster-but-sparser native mode mentioned in the schema.

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?

It gives concrete use cases (文章内容分析、公众号监测、RAG 语料入库), which tells the agent when this tool fits. It doesn't explicitly exclude anything or name a sibling alternative, though the H5/native recommendation inside the description effectively guides variant choice.

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