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

There are no annotations, so the description must disclose behavioral traits. It only mentions 'Billing per call: 1 Credits', which is a cost detail, not behavior. It does not disclose whether the operation is read-only, has side effects, requires authentication, or anything about the response.

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 extremely brief, but this is under-specification rather than efficient conciseness. It does not provide enough information to be helpful. While it is short, it lacks essential context, so it cannot earn a higher score.

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 is simple (one parameter), but with no output schema and no annotations, the description must explain what happens. It fails to describe the return value, required inputs (the parameter is not marked required), or any preconditions. The description is inadequate for a functional 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 schema provides 100% coverage with the parameter description 'id or https://vm.tiktok.com/xxxxxxx'. The tool description adds nothing beyond that, so the baseline score of 3 is appropriate given that 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 'get playlist info' restates the title with minimal added meaning. It does not specify what specific playlist information is returned or how it differs from siblings like get_mixList or get_mixPosts. The verb 'get' is clear but the resource is vague.

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 alternatives. Sibling tools such as get_mixList or get_mixPosts exist, but the description offers no context or exclusions to help the agent choose correctly.

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