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

The description discloses two useful behavioral traits: 'best-effort' signals possibly incomplete or unreliable results, and 'keyless' signals no authentication is required. However, with no annotations, it still omits failure modes, rate limits, and what kind of input produces an error.

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 short and readable, and the 'best-effort, keyless' caveats add useful information without padding. There is minor redundancy in repeating 'TikTok Profile' and 'TikTok user stats', but no real wasted sentences.

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?

For a single-parameter tool, the description is incomplete because it never explains what to put in q, and it does not indicate whether calling with the default empty q is valid. The 'best-effort, keyless' note adds useful context, but the missing parameter semantics make correct invocation uncertain.

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?

With 0% schema coverage, the description must compensate for the undocumented 'q' parameter. 'TikTok user stats' weakly implies that q is a TikTok user identifier, but it never explicitly says q should be a username or how it should be formatted. This leaves the sole parameter open to guesswork.

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 identifies the resource (TikTok users) and the expected output (stats), with 'Profile' implying a lookup operation. It is clearly distinguished from siblings by platform, though it lacks an explicit verb like 'fetch' or 'retrieve' and does not define what counts as 'stats'.

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 given for when to use this tool versus any alternative. The description does not mention prerequisites, expected query format, or situations where this tool should not be used.

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