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

Beyond the destructive/openWorld annotations, it discloses that posts go to live external platforms, that the call is not retried server-side and needs distinct content per call, the 402 entitlement failure mode, and that it is free (no credits). This is exactly the operational context annotations cannot express.

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?

It is a dense single block but front-loads the core purpose and every clause carries functional information (conditional URL rules, timing logic, drafts, failure modes). It could be broken into clearer segments, but there is little waste.

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 15-parameter mutation tool with nested objects and no output schema or schema descriptions, it covers the highest-risk behaviors (live posting, entitlement 402, no retry, timing modes). It leaves several parameters and the return shape unexplained, but the safety-critical context is present.

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?

With 0% schema description coverage, the description carries the burden and explains the assetKind-to-URL conditional rules, scheduledAt/addToQueue exclusivity, and the platformOverrides post_mode draft trick well. However, many of the 15 parameters (title, tags, visibility, saveAsDraft, thumbnailUrl, accountVariants, first_comment) receive no mention, so it compensates only partially.

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 opening sentence states a specific verb pair (publish/schedule), the resource (post), the target (connected accounts on a brand), and the fan-out scope in one call. An agent can distinguish this from siblings like create_tiktok_carousel or publish_to_managed_account without opening the schema.

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 gives explicit when-to-use rules for the timing modes (omit both to publish now, scheduledAt for a time, addToQueue for the queue, mutually exclusive) and points to get_video/import_asset_from_url/create_upload for sourcing URLs. It stops short of naming alternative siblings or when-not-to-use cases, so it is clear but not fully routing.

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