publish_now

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

No annotations are provided, so the description bears the full burden. It discloses immediate publishing, folder-to-carousel behavior, and account targeting, which is useful. However, it does not mention that publishing is irreversible/live, authentication requirements, or what happens to uploaded files, leaving some behavioral gaps for a mutation tool.

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 concise sentences, front-loaded with the core action, then adding carousel behavior and account targeting. Every sentence carries useful information with no filler or repetition of the tool name.

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 moderate complexity and full schema coverage, the description adequately explains purpose, platforms, file/folder input, and account selection. It does not explain the return value or error cases, but with no output schema, this is a minor gap for an otherwise clear publish action.

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 covers 100% of parameters with descriptive text, so the baseline is 3. The description largely reiterates schema details, such as folder paths for carousels and account_ids precedence. It adds little beyond the schema, mainly cross-referencing list_connections, which is already in the 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?

The description clearly states the verb and resource: 'Upload local file(s) and publish immediately' to TikTok, Instagram, and/or YouTube. It also distinguishes itself from sibling tools by emphasizing immediacy, unlike schedule_post or send_to_drafts, and by describing the carousel behavior for folders.

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 provides explicit guidance on when to use account_ids vs platforms: 'Use account_ids (from list_connections) to target a specific account when you have multiple accounts on the same platform.' It does not explicitly mention exclusions or alternatives like scheduled posting, but the 'immediately' phrasing and sibling tool names imply the distinction.

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