Post or schedule a TikTok video

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

With no annotations, the description must disclose behavioral traits. It mentions 'connected browser profile' and 'native scheduler,' but omits critical details like account prerequisites, how video inputs are handled, post-publication effects, rate limits, or error conditions. This leaves significant behavioral gaps for an agent.

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 a single sentence, which is concise, but it is under-specified for a tool with 10 parameters. It does not front-load essential usage details and is more close to a summary than a helpful guide, making it inadequate for the tool's complexity.

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 10 parameters, no annotations, and no output schema, the description is far too sparse to enable correct invocation. It fails to explain the multiple video input options, scheduling constraints, privacy settings, or account requirements, leaving the agent without essential context.

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 30%, and the description adds no parameter semantics. It does not explain the differences between video_url, video_path, and video_base64, nor the meaning of privacy values, schedule_at format, or other fields. The description fails to compensate for the low schema coverage.

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 clearly states the tool publishes or schedules a TikTok video, specifying the action (publish/schedule), resource (TikTok video), and context (local video via browser profile or native scheduler). This distinguishes it from sibling tools like tiktok_scheduled (listing) and tiktok_cancel_scheduled.

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 description implies the tool is used for posting or scheduling videos, but does not explicitly state when to choose it over alternatives or mention any exclusions. There is no reference to sibling tools or conditions that would make other tools preferable.

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