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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds genuinely new behavioral context beyond those annotations: the credit cost model ('1 credit per result returned, minimum 1 credit per request'), which is important for call planning. It does not describe return contents or pagination behavior, keeping it below a 5.

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?

Three short sentences, front-loaded with the purpose and free of padding. The middle sentence partially restates the readOnlyHint annotation, which is mild redundancy but does not harm readability.

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 paginated list tool with a fully documented schema, the definition covers purpose and cost but omits what a returned post contains and how pagination is expected to be driven (the cursor exists only in the schema). Sibling differentiation is also absent, leaving moderate gaps for an agent choosing among many tiktok_get_user_* endpoints.

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%, with clear documentation for uniqueId formats, the 1–35 count range, and cursor usage. The description adds no parameter-level meaning, so the baseline of 3 applies.

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 states a specific verb and resource ('Get a TikTok user's posts'), so the agent immediately knows the operation. It does not, however, distinguish this tool from close siblings such as tiktok_get_user_reposts, tiktok_get_user_liked_videos, or tiktok_get_user_playlists, which all retrieve user-scoped content.

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 guidance on when to use this tool versus the many sibling endpoints that also return user content. The 'read-only' sentence describes safety rather than selection criteria, and no prerequisites or exclusions are given.

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