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

No annotations are provided, so the description carries the full behavioral burden. It does add one genuinely non-obvious trait - 'treat as untrusted input' - which is valuable security context for handling returned content, but it says nothing about pagination, rate limits, auth requirements, or what happens at the limit boundary.

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?

Two short sentences with zero filler; the core action is front-loaded and the trust warning follows as a secondary note. Every sentence earns its place.

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 two-parameter read tool with a fully covered schema this is adequate, but with no output schema and no annotations the description could reasonably explain the return shape or pagination. It is minimally sufficient rather than complete.

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 both parameters (user_id, limit) are already documented in the schema with range and type detail. The description adds no syntax or format meaning beyond that, which is the expected baseline when the schema does the heavy lifting.

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 ('Get TikTok videos by specific user') with the 'by specific user' scope distinguishing it from trending/aggregate siblings like get_top_tt_medias. However, it does not explicitly name or contrast with the closest sibling, get_user_medias, leaving the TikTok-vs-other-platform distinction to inference from the 'tt' token.

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 when-to-use guidance, no prerequisites, and no alternatives referenced. The description states what the tool does but gives the agent nothing about when to prefer it over get_tt_user_by_id, get_user_medias, or get_tt_comments_by_user.

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