tiktok_get_user_posts

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

Since no annotations are provided, the description carries the full burden. It discloses that the tool returns post IDs, upload dates, and URLs, which is useful. However, it does not mention any behavioral traits like rate limits, authentication needs, or pagination behavior beyond 'max' parameter. The description is adequate but not thorough.

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 a single sentence that efficiently captures purpose and output. It is front-loaded with key information. No unnecessary words, but could be slightly more structured with examples or usage hints.

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?

Given the tool's relative simplicity (2 params, no output schema, no nested objects) and sibling context, the description is sufficient for basic understanding. However, it lacks guidance on when to use this vs tiktok_get_user_analytics or tiktok_download_user_media, and does not explain what happens if the max is exceeded or if the user has no posts. A more complete description would include a note about the scope of 'recent' and any limitations.

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%, so baseline is 3. The description adds no additional meaning beyond the schema; the 'max' parameter is already described with default and purpose, and 'username' is well-documented. The description reiterates that username accepts @ or plain or URL, which is helpful but not a significant addition.

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 clearly states it lists recent post IDs, upload dates, and URLs for a TikTok user or profile URL. The verb 'list' and resource 'TikTok user posts' are specific, but it does not distinguish from siblings like tiktok_extract_post or tiktok_download_post, which have different purposes.

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?

The description implies usage for fetching recent posts from a user, and mentions that the input can be a username or profile URL. However, it lacks guidance on when to use this tool versus alternatives (e.g., tiktok_download_user_media for downloading, tiktok_get_user_analytics for analytics). No exclusions or prerequisites are mentioned.

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