douyin_get_user

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

No annotations are provided, so the description carries the full burden. The description indicates a read operation ('获取信息'), which is consistent with the tool name. However, it does not disclose any potential rate limits, authentication requirements, or what happens if the account_id is invalid. The mention of '优质库' hints at data freshness or quality but lacks specifics, so a 3 is appropriate.

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 short (one sentence plus a clarification on the parameter). It is front-loaded with the main purpose and immediately follows with the key detail about id matching. Every part serves a purpose, though it could be slightly more structured with explicit labels.

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?

Given there is only one parameter and an output schema exists, the description covers the essential points: what the tool does and how to use the input. It doesn't explain the return format, but the presence of an output schema mitigates this need. It is complete enough for a simple lookup tool.

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 has only one parameter (account_id) with no description (coverage 0%). The description adds significant value by explaining that account_id can be a unique_id, short_id, or uid, and that any of these can be used to match. This goes well beyond the bare schema and compensates for the lack of schema-level documentation, earning a 4.

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 clearly states '获取抖音账号信息' (get Douyin account info) with a specific verb and resource. It also notes the data source is an '优质库' (high-quality database), which adds useful context. While it doesn't explicitly differentiate from siblings like 'xiaohongshu_get_account', the platform-specific name and description already signal this is for Douyin, so a 4 is appropriate.

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 implicitly states that the tool is used to look up a user by account_id, and even clarifies the id matching options. However, it does not provide explicit guidance on when to use this tool versus alternatives like 'douyin_search_users' or 'douyin_get_user_works', nor does it mention any prerequisites or exclusions. Thus, a 3 for implied usage.

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