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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful behavioral context beyond that: it requires an exact forum name and points to a fallback tool when the name is uncertain, which prevents a common failure mode. It does not cover failure behavior for a wrong-but-plausible name or any rate-limit/auth considerations, so it falls short of a 5.

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 purpose in sentence one, followed by two tight conditional sentences that each route the agent to a specific sibling. No filler, no repetition of schema content.

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?

An output schema exists, so return-field detail is not required, and annotations already carry the read-only/open-world profile. What remains necessary for correct invocation — exact-name input plus fallback routing for name discovery and post browsing — is fully present.

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% and the single forum_name parameter already carries rich constraints (no trailing '吧', no URL or numeric ID, no URL encoding). The description only restates the 'exact name' requirement without adding syntax or format detail beyond the schema, 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?

The first sentence names a specific verb (获取) plus resource (贴吧) and enumerates exactly what is retrieved: 简介、标语、建吧日期、关注人数、帖子统计、友情链接贴吧. It also distinguishes itself from two named siblings (baidu_tieba_search_posts_in_forum, baidu_tieba_get_forum_posts), so an agent can separate it from the adjacent tools without opening any 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?

Explicit conditional routing: if the exact forum name is unknown, call baidu_tieba_search_suggestions first to obtain forum_name; for keyword-based post lookup use baidu_tieba_search_posts_in_forum; for keyword-free browsing use baidu_tieba_get_forum_posts. Both the precondition (accurate name) and the alternatives are stated.

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