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

Annotations already declare readOnlyHint=true and openWorldHint=true, so no safety contradiction exists. The description adds the '公开资料' (public data) scope, which somewhat clarifies behavior, but it does not disclose details such as rate limits, required authentication, or response shape. Given the annotations cover the core safety profile, this is adequate but not rich.

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?

The description is one short sentence with no filler, front-loading the core purpose and input requirement. For a single-parameter read-only tool, this length is appropriately concise and every word contributes value.

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?

The tool has one required parameter, an output schema, and annotations indicating read-only/open-world behavior, so the description does not need to explain return values. The description is sufficient for a simple public-profile lookup, though it could slightly strengthen usage guidance by naming the sibling alternative for ID-based lookups.

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?

The input schema already describes profile_url with 100% coverage and includes an example link. The tool description merely refers to 'TikTok 用户主页链接', adding no new parameter meaning beyond what the schema provides. Thus the baseline score of 3 is appropriate.

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 uses a clear verb ('获取', 'get'), a clear resource ('用户公开资料', 'user public profile'), and specifies the input mechanism ('根据 TikTok 用户主页链接'). This directly distinguishes the tool from siblings like tiktok_get_user_info_by_tiktok_id, which operate on a TikTok ID rather than a profile URL.

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?

The description implies the tool should be used when a TikTok user profile URL is available, but it does not explicitly state when to use it over alternatives or when not to use it. No guidance is given about choosing between this tool and tiktok_get_user_info_by_tiktok_id based on whether the caller has a URL or an ID.

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