douyin_get_user_works

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

No annotations provided, so description carries full burden. It discloses that offset increments by 20 per page, and sort_type options (0=default, 2=newest, 4=hottest). It does not disclose rate limits, auth requirements, or result count 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?

The description is concise with 3 sentences covering purpose, prerequisites, and parameter details. No fluff. Could be slightly better structured but efficient.

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?

No annotations, but description covers purpose, parameter usage, and pagination behavior. Has output schema so return values are covered. Missing info on rate limits, but adequate for a list 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?

Schema coverage is 0%, so description must compensate. It explains the meaning of all key parameters: account_id/author_url/sec_user_id (at least one), offset (pagination +20), sort_type (values 0,2,4). This adds significant value beyond the schema.

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 states '获取抖音账号作品列表' (get Douyin account works list), which is a specific verb and resource. It is clearly distinct from sibling tools like 'douyin_get_work' (single work) and 'douyin_search_users' (search users), though not explicitly differentiating.

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 provides usage conditions: at least one of account_id/author_url/sec_user_id must be provided. It also hints at pagination with offset +20. However, it does not explain when to use this vs other tools like douyin_get_work or when not to use it.

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