publish_to_tiktok

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

With no annotations, the description carries the full burden. It discloses the rate limit, draft mode behavior, and parameter-specific constraints (e.g., caption max 89 chars, visibility enum values). It lacks error handling or permission details but provides substantial behavioral context.

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 well-structured with a header, note, and args list. Each parameter gets a concise line. It is slightly long due to the parameter count, but 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?

Given the tool's complexity (15 params, no output schema, no annotations), the description is quite complete: it covers all inputs, the rate limit, and suggests a draft alternative. It omits return value/error behavior, but the coverage is strong for the complexity.

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%, but the description compensates fully by explaining all 15 parameters, including default values, allowed enum values for visibility, post_mode, and upload_type, and character limits. This adds essential meaning beyond the bare schema.

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?

Description explicitly states 'Publish a completed video to TikTok with all settings provided directly (no automation needed)', giving a specific verb and resource. It also distinguishes from automation-based tools by highlighting 'no automation needed'.

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?

Mentions 'no automation needed' to differentiate from automation flow, and gives explicit guidance about TikTok's 6-publish limit: 'Use MEDIA_UPLOAD (draft) to avoid this.' However, it does not directly name alternative sibling tools like publish_video_via_automation.

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