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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description still adds real value beyond that: reverse-chronological ordering, the shape of returned records, and a per-call billing model with success-only charges and automatic refunds on failure or empty results.

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 tight sentences that front-load purpose, then return shape, then usage, then pricing — every clause carries information. Minor redundancy between "获取用户推文列表" and "返回该账号发布的内容列表" keeps it from a 5.

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 supplies what the return looks like (ordered records with content ID and basic engagement metrics), plus the billing caveat an agent needs before spending money. For a paginated read-only list tool, nothing essential is missing.

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 baseline would be 3, but the description adds a genuinely non-obvious constraint: screen_name and rest_id are mutually exclusive alternatives. The schema marks all four parameters optional with no such hint, so this prevents an agent from omitting both.

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 ("获取用户推文列表") and scopes it to a single account, which distinguishes it from account-agnostic siblings like tw_keyword_search. It never names an alternative tool, so differentiation is inferred from scope rather than explicit.

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 when-to-use scenarios: monitoring posting frequency, content strategy, or bulk-collecting content IDs. It provides no when-not guidance and does not point to tw_post_detail or tw_keyword_search for the cases this tool doesn't cover.

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