douyin-account-diagnosis

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 discloses the high-level action (querying data and generating a report), but does not describe side effects, report contents, data freshness, required permissions, or any limitations. It adds minimal behavioral context beyond the obvious purpose.

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 a single clear, front-loaded sentence that immediately communicates the tool's purpose and its core behavior. There is no filler or redundancy.

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 the simple one-parameter schema, the description is adequate for basic invocation. However, there is no output schema, and the description does not clarify what the diagnosis report contains or how the agent should interpret the generated report, leaving some ambiguity about the tool's full behavior.

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 schema already documents accountId as the Douyin account ID. The description only restates that account data is queried, adding no meaningful parameter semantics beyond what the schema provides.

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 and resource: querying Douyin account data and generating a diagnosis report based on account ID. This clearly distinguishes the tool as an account-level Douyin diagnosis tool, though it does not explicitly contrast it with sibling tools.

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 implied through the description: it is meant for diagnosing a Douyin account from its account ID. However, there is no explicit guidance on when to choose this tool over alternatives such as xiaohongshu-account-analyzer or kuaishou-accounts, and no exclusions or prerequisites are mentioned.

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