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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and network behavior are covered structurally. The description adds the concrete payload it returns (followers, following, likes, video count), but says nothing about data freshness, required permissions, or whether metrics are cached — modest added value on top of the annotations.

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 no filler; the resource and the returned fields come first and nothing is restated.

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?

With no output schema and only two well-documented parameters, the description's enumeration of returned metrics carries the return-value burden adequately for a simple read. Minor gap: no mention of error cases or what happens when the account has no profile, but that is not critical here.

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%, and the schema even documents the accountId/profileId relationship (profileId optional when accountId is given, must agree if both supplied). Baseline 3 applies: the description adds no parameter meaning beyond what the schema already 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?

States a specific verb (Return) and resource (TikTok account's profile and aggregate statistics) and enumerates the returned metrics. It is clear what the tool does, but it does not differentiate itself from close siblings such as get_tiktok_account_insights or get_tiktok_creator_info, so an agent must infer the distinction from names alone.

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?

There is no statement of when to use this tool versus get_tiktok_account_insights, get_tiktok_creator_info, or get_tiktok_video_insights, all of which live in the same TikTok namespace. No prerequisites or exclusions are given; the agent must guess from the name.

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