tiktok get uploaded video

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint, but the description adds useful behavioral context beyond those flags: the result is only ready once positive duration and dimensions exist, and the call does not upload again. This helps set expectations for polling or post-upload checks. No contradiction with annotations.

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 three short sentences with no filler: purpose, readiness behavior, and non-upload clarification. The core identity is front-loaded, and every sentence contributes useful information.

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-only tool with full schema coverage, rich safety annotations, and an output schema, the description is complete. It tells the agent what is read, when the result is ready, and what the call does not do, leaving no essential operational gap.

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?

The input schema fully describes both parameters (advertiserId and videoId) with 100% coverage, so the description does not need to repeat their meaning. It also adds no additional parameter-level nuance, which is acceptable given the schema's clarity.

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 action and resource: 'Read one uploaded video from this advertiser’s media library.' It clearly signals a single-item read rather than a list or upload, which helps distinguish it from tools like tiktok_list_ad_videos, although no sibling is explicitly named.

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 readiness condition ('Returns ready only after its media information is available with positive duration and dimensions') implies this tool should be used to check an uploaded video after processing. However, it does not explicitly say when to choose this over similar video-related siblings, so the guidance remains implied rather than explicit.

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