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

With no annotations, the description carries full responsibility for behavioral disclosure. It merely says 'TikTok Live' with no indication of side effects, permissions, data returned, or whether it is a read or write operation. This is a complete black box.

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?

At two words, the description is under-specified rather than concise. It provides no meaningful content and fails to convey core information, making it inefficient for the agent despite its brevity.

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 one required parameter, no annotations, and no output schema. The description does not explain the return value, behavior, or any context needed for invocation. It is completely inadequate for a tool with zero external structure providing context.

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 schema provides a 100% description coverage for the single 'handle' parameter, describing it as 'TikTok handle'. The tool description adds no additional meaning, but the baseline for high schema coverage is 3, and the schema already documents the parameter adequately.

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 'TikTok Live' identifies the platform and feature, but lacks a verb or specific resource. It does not distinguish this tool from siblings like scrapecreators_tiktok or scrapecreators_tiktok_shop, and it essentially restates the tool name without explaining what action is performed.

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?

No guidance is provided on when to use this tool versus alternative scrapecreators_* tools. The description does not mention any specific use case, prerequisites, or exclusions, leaving the agent without direction for selection.

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