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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so safety and repeatability are covered. The description's real contribution is the billing model (¥0.1 per call, charged only on success, auto-refund on failure or empty result), which is genuinely useful cost context an agent cannot get from annotations. However, it says nothing about auth requirements or rate limits beyond what the schema's _token field implies.

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 purpose, then return payload, then use cases, then pricing. Each clause carries information and there is no filler, though the return-field enumeration somewhat duplicates what a caller would discover at runtime.

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?

With no output schema, the description usefully enumerates expected return fields (正文, 转发/评论/点赞数, 发布者, 发布时间, 配图), and the pricing note covers the commercial side. A tool this simple is adequately covered; only the absence of auth/rate-limit notes and post_id provenance keeps it from a 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 description coverage is 100%, with both post_id and _token documented in the schema itself. The description adds no format or syntax guidance for post_id (e.g., where to obtain it or whether short IDs work), so it neither compensates nor detracts — baseline 3.

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 scopes the payload ('含互动量'). This is enough to separate it from weibo_post_comments or weibo_keyword_search, though it never names those siblings explicitly, so the differentiation is inferred rather than 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 three concrete usage scenarios — single-post engagement analysis, material archiving, and as the entry point for a batch task. It stops short of explicit when-not-to-use guidance or naming the alternative tool for comment retrieval, so routing is clear but not fully disambiguated.

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