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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description mostly repeats the read nature with '[read]' and adds unrelated downstream ad context rather than disclosing listing behavior such as pagination, ordering, or rate limits.

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 short, but the second sentence is a long tangent about create_ads_campaign and ad identity that does not help callers list videos. The read scope is front-loaded, but the content is poorly allocated.

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?

With four parameters, 0% schema coverage, and no output schema, the description should explain pagination defaults and return structure. It only partially covers the account identifier parameters and omits page/per_page semantics, leaving the caller with gaps.

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 0%, so the description must compensate. It clarifies that tt_account_id and tt_account_uuid are alternative account identifiers, but it ignores page and per_page entirely and introduces tt_video_id, which is not a parameter of this tool.

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 identifies the resource and scope: a TikTok account's uploaded videos, keyed by tt_account_id or tt_account_uuid. This is clear enough to understand what the tool returns, but it never explicitly says 'list' and does not differentiate from the sibling search_tt_videos tool.

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 search_tt_videos or other listing tools. The second sentence explains downstream ad-creation usage of tt_video_id, but that is not guidance for invoking this listing tool.

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