kuaishou-accounts

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 does disclose the fuzzy-search behavior, return fields, and a downstream use for kwaiId, which is helpful. However, it does not mention pagination behavior, result limits, data freshness, authentication needs, or potential empty results. These are gaps for a tool that might be called programmatically.

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 compact and front-loaded with the core purpose and return values, followed by explicit use cases and trigger words. The use-case list has some redundancy (e.g., '查快手账号' and '搜快手达人' overlap with the main purpose), but the overall structure is efficient and leaves little waste.

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?

For a simple search tool with one required parameter and no output schema, the description covers the essential return items and even points to the sibling tool for works lookup. It is complete enough for an agent to call correctly, though it could be more explicit about pagination defaults. The schema already handles page/pageSize, so the absence of that detail in the description is acceptable.

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 description coverage is 100%, so the baseline is 3. The description adds the '模糊搜索' (fuzzy search) nuance for accountName, which is useful beyond the schema's plain '快手账号名称'. Page and pageSize are already fully documented in the schema, so no additional meaning is needed there. Overall, the description adds only marginal semantic 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 a specific verb ('搜索'), resource ('快手账号'), and mechanism ('通过账号名称模糊搜索'), and lists concrete return fields (kwaiId、昵称、头像、简介). It also distinguishes itself from the sibling kuaishou-account-works tool by explicitly noting that kwaiId can be used to query the account's works list. The trigger words further reinforce the intended use.

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 clearly states when to use this tool: '当用户需要按名称搜索快手账号、查找快手博主、定位达人账号、获取账号kwaiId时使用'. This provides explicit context for invocation. However, it does not explicitly mention when not to use it or name alternative sibling tools (e.g., kuaishou-search), though the kwaiId-to-works pointer indirectly helps route to kuaishou-account-works.

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