douyin_search_users

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

No annotations are provided, so the description carries the full burden. It only mentions pagination via offset but does not disclose how the '优质库' selection works, rate limits, authentication requirements, or whether search results include full profiles. For a search tool, critical behavioral context is missing.

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 extremely concise—two sentences that get to the point. The key constraint (keyword required) and pagination detail are front-loaded. No filler or duplication of schema fields.

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 3 parameters, no annotations, and an output schema is present but the description is minimal. Given the sibling landscape with many search tools and the lack of guidance on 'sort_type' or result format, the description is not complete enough for a reliable agent invocation.

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 the description must compensate. It explains that 'keyword' is required and that 'offset' starts at 0, but does not clarify the purpose or valid values of 'sort_type'. With 3 parameters and only partial explanation of two, the baseline 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 clearly states the verb 'search' and the resource '抖音账号', and distinguishes its scope from siblings like 'douyin_get_user' (single user retrieval) and 'douyin_search_articles'. The mention '优质库' implies a curated user database, which adds specificity.

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 states that 'keyword' is required and gives the offset behavior, but it does not explain when to use this tool over alternatives like 'douyin_get_user' (for known user details) or when to choose different sort types. No when-not-to-use or alternative guidance is provided.

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