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

Annotations only cover readOnly/openWorld, but the description adds genuine behavioral context beyond them: pagination is supported, replies are not included, no sorting is offered, lists and media are not guaranteed complete, and an empty page token signals the end of the readable list. These caveats materially affect how an agent should interpret 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?

Three short lines, each front-loaded with purpose, then routing, then caveats. No sentence is redundant against the others or against the schema.

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 a full output schema, 100% parameter coverage, and annotations already declaring the safety profile, the description covers what remains: routing between siblings and the incompleteness/termination semantics of the result set. Nothing an agent needs to call this correctly 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 description coverage is 100%, so page_token and profile_url are already fully documented in the schema (format, first-call-empty rule, token reuse constraints). The description reinforces pagination but adds no new syntax or format detail, so the 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?

States a specific verb and resource (按主页链接读取该用户发布的主题帖) plus explicit scope boundaries: excludes reply activity and provides no sorting. This cleanly distinguishes it from the by_user_id sibling and from the comment/post-detail tools in the sibling list.

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?

Explicitly routes the agent: prefer this tool when profile_url is available, use baidu_tieba_get_user_posts_by_user_id when only a numeric user ID exists. The condition that selects the alternative is named outright, leaving nothing to inference.

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