get_v2_user_medias_by_secUid

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false. The description adds genuinely new operational context beyond them: it is a live request to TikTok billed per call, and results are paginated one page per call via `max_cursor`. It does not cover rate limits, auth requirements, or quota failure behavior, so it falls short of 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 tightly packed sentences, front-loaded with the core action before routing guidance and parameter notes. No filler or repetition of the title, and the trailing endpoint notation is a useful compact reference.

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 read tool with no output schema, the description covers purpose, routing, pagination mechanics, and cost, with annotations carrying the safety profile. It doesn't characterize the returned video fields, but that is a minor gap for a list endpoint.

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 only 33% (`count` and `max_cursor` have no schema descriptions, `secUid` just says 'User sec_uid'), so the description must compensate. It does: it explains that `secUid` comes from the profile tool, that `count` sets page size, and that `max_cursor` pages through results. It omits the count max of 50 and cursor format details, which keeps it from a 5.

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?

Opens with a specific verb+resource and scope: 'List a TikTok user's videos, one page per call.' It explicitly distinguishes itself from the two nearest siblings (`get_v2_user_likes_by_secUid` for liked videos, `get_v1_media_by_id` for a single video), so an agent can route without opening any schema.

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?

States when to use it ('read an account's content') and names both alternatives with the condition that selects each, including where to obtain the required `secUid` (from the profile tool). Nothing about tool selection is left to inference.

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