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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuinely useful behavioral context beyond that: results are a single page with no pagination, and profile_url is a usable handle for downstream tools. It stops short of describing matching behavior or result volume limits.

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?

Two sentences, front-loaded with the core purpose followed by the downstream-usage note and the no-pagination constraint. Nothing is redundant, though the second sentence could be marginally tighter.

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-value explanation is not required, and the description correctly focuses on the non-pagination constraint and the profile_url handoff. Given a single-parameter read-only tool, this is essentially complete, with only matching semantics left implicit.

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 keyword parameter is already fully documented in the schema, including the negative cases (no profile links, numeric IDs, or pagination tokens). The description adds no parameter-level 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?

The description names a specific verb and resource (按关键词查找百度贴吧用户) and quantifies the result shape ('精确匹配和相关用户的单页结果，不支持分页'), which immediately separates it from the post/forum search siblings. An agent can tell what this tool returns without opening 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 routing guidance: when a user homepage link already exists, use the user-profile or user-posts tools instead, and it flags that pagination is not supported. However it does not contrast itself with the other search siblings (search_general, search_posts, search_posts_in_forum), so the selection context is clear but not fully enumerated.

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