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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered by structured data. The description adds that pagination is cursor-based and that sorting is available, but gives no behavioral detail such as page size, rate limits, or whether an empty cursor means the end of results. With annotations carrying the safety burden, a 3 is appropriate.

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 that names the resource, the required identifier, and both optional capabilities with zero filler. Nothing could be removed without losing information.

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 explained, and annotations cover the read-only safety profile. The description addresses all three parameters at a high level, leaving only minor gaps such as where secUid is sourced and how pagination terminates.

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 already documents cursor semantics, the secUid requirement, and the exact sort_type values (0 latest, 1 popular, 2 oldest). The description merely restates 'cursor pagination and sort mode' without adding format, default, or edge-case detail beyond the schema, so the baseline 3 holds.

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 and resource ('Returns posts from a TikTok profile') and names the identification key (secUid), so an agent knows exactly what it retrieves. It does not differentiate from nearby siblings like tiktok_profile or tiktok_post, which could plausibly return overlapping data, so it falls short of a 5.

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?

Usage is only implied: the requirement of a secUid hints that a profile lookup must happen first, and 'cursor pagination' hints at iterative fetching. There is no explicit statement of when to prefer this over tiktok_post, tiktok_profile, or tiktok_search, and no alternative is named.

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