douyin_account_overview

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

Annotations contain only a title, so the description bears the full behavioral burden. It usefully discloses the data source (creator center homepage / data center), which hints at a scraping path that likely depends on an authenticated session, but it never states the auth requirement, whether data is live or cached, or any rate limiting.

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 sentence, front-loaded with the scope ('account-level data') followed by the metric list and the data source in parentheses. It is efficient, though the trailing '等' leaves the metric set open-ended rather than definitive.

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?

There is no output schema, so enumerating the returned metrics in the description is valuable compensation. However, for a zero-parameter tool with no annotations beyond a title, the definition omits the preconditions an agent needs: login state required, and what happens when the account is not authenticated or has no data.

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 tool takes zero parameters, so there are no parameter semantics to explain; the baseline of 4 applies. The description correctly implies the call is parameter-free by presenting the tool as a fixed account-level snapshot.

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 resource (account-level data) and enumerates the metrics returned: total followers, new followers, views, likes, profile visits, completion rate. The phrase '账号层面' implicitly distinguishes it from the video-level sibling douyin_video_stats, but it never names that sibling, so the differentiation is inferred rather than explicit.

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?

Usage is only implied: '账号层面的数据' signals the aggregate/account scope, which lets an agent infer this is for account summary rather than per-video stats. There is no explicit when-to-use, when-not-to-use, or named alternative among the many related siblings (douyin_video_stats, douyin_my_videos, douyin_user_profile).

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