douyin_user_profile

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the login requirement ('需要已登录'), which is the key operational trait, but omits whether the call is read-only, pagination/rate-limit behavior, or what happens on a stale/invalid sec_user_id.

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?

A single dense sentence, front-loaded with the purpose followed by the return fields and the login caveat. Nothing is wasted, though the chained parentheticals make it slightly less scannable than a two-sentence layout.

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 compensates by enumerating the returned profile fields and noting the optional works list plus the login prerequisite. An agent has enough to call it correctly, though read-only status and error/failure behavior remain unstated.

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 the baseline is 3, but the description adds real value beyond the schema by specifying the sec_user_id format (MS4wLjABAAAA…) and its source in sibling tools, which helps the agent obtain a valid value.

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 ('看某个抖音用户的主页信息') and enumerates the exact fields returned (昵称、抖音号、简介、IP 属地、粉丝/关注/获赞/作品数). It also flags the optional works list. It does not explicitly contrast with the sibling douyin_my_profile, so it falls just short of a 5.

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 concrete context: this needs a login to return the works list, and explains where to obtain sec_user_id (from the author field of douyin_search_videos / douyin_video_detail). It does not state when NOT to use it or name an alternative tool, so no explicit exclusions.

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