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

No annotations are repeated and the description correctly conveys a pure fetch, adding the specific payload fields. It does not mention auth requirements, rate limits, or whether a missing/private creator yields an error versus empty data. Note the annotations set readOnlyHint=false for what the description presents as a read — an inconsistency worth flagging, though the fault likely lies in the annotation rather than the text.

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 the resource and returned fields, zero filler, zero restatement of the title.

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?

An output schema exists, so return values need not be described, and annotations carry the safety profile. What remains unaddressed is the practical calling constraint — that the agent must supply handle or user_id — which is the main thing an agent could get wrong 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 coverage is 100% and the schema already explains that user_id is 'an alternative to handle' and that '@' is optional, so the description adds nothing on parameters and the baseline 3 applies. The one operational gap is that neither schema nor description states that at least one identifier is required (required parameters: 0).

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 names a specific verb and resource and enumerates the payload (bio, follower/following counts, stats), so an agent knows exactly what it returns. It does not explicitly differentiate itself from cross-platform siblings like instagram_profile or x_profile, but the TikTok scoping in name+description makes the boundary obvious in practice.

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 explicit when-to-use statement, no mention of when to prefer tiktok_video or the generic api_request, and no prerequisites. Usage is only implied by the platform named in the description; an agent must infer it from the tool name.

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