douyin_health_check

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

With no annotations, the description carries the full behavioral burden. "Return... for diagnostics" implies a non-mutating read check, and the empty schema confirms no arguments, but it says nothing about auth prerequisites, rate limits, side effects, or what errors mean for a health check.

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 front-loaded sentence with zero waste. The verb, the returned data, and the intent all appear in one pass.

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 and no annotations, so the description is the only source of information about return values. It names "login status" and "profile health" but leaves the concrete shape and meaning of "profile health" undefined, which is a real gap for a diagnostics 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?

The tool takes zero parameters, so per the baseline there are no parameter semantics to document. The empty schema is self-explanatory and the description adds nothing misleading.

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?

States a clear verb (Return) and resource (login status and profile health) with an explicit purpose (for diagnostics). It does not, however, distinguish itself from the sibling douyin_login_status, which plausibly covers overlapping territory, so an agent must infer the difference.

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?

"For diagnostics" gives an implied context for use, which is better than nothing. But there is no explicit when-to-use statement, no when-not, and no pointer to the alternative douyin_login_status, so routing between the two is left to inference.

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