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

Though annotations already declare readOnlyHint and idempotentHint, the description explains what that means in practice: no post is sent until a person presses Post, TikTok requires viewer choice and disclosure confirmation, and the pipelines:write scope is required. No contradiction with the 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 dense but not padded; the core behavior and the key exclusions come first. It is longer than average because it covers several edge cases, but each sentence contributes a distinct operational constraint.

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 7-parameter tool with no output schema, the description covers the full decision context: prerequisites, person-in-the-loop confirmation, alternative pipeline path, channel selection, and required scope. Nothing essential for correct use is missing.

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 coverage is 100%, but the description adds operational semantics beyond the schema: the video must come verbatim from list_assets or a finished run, channelId is used only when more than one channel is connected, and TikTok treats title as a caption with hashtags. This meaningfully helps correct invocation.

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 leads with a specific verb and resource: prepare a post of one finished video to a connected YouTube channel or TikTok account. It also states the distinguishing behavior, 'posts nothing itself', which separates it from confirm_publish and publish_pipeline.

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?

It states exactly when to call it ('only when the person asked to publish'), names the alternative for panel-less clients (pipeline ending in youtube-upload/tiktok-upload), and gives preconditions like calling connect_channel first when no channel is connected. This leaves no ambiguity about selection.

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