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

Annotations already show this is a non-read-only, non-destructive write operation. The description adds useful behavioral context beyond annotations: DIRECT_POST publishes to the TikTok profile while UPLOAD creates an inbox draft, and segment arrays chain replies from a root post. No contradiction with 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?

Three focused sentences: the first states the core purpose, and the following sentences add high-value platform-specific parameter guidance. There is no fluff or repetition of schema content.

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 10-parameter, multi-network creation tool with no output schema and zero schema description coverage, this description is incomplete. It omits scheduling modes (DRAFT/NOW/SCHEDULE), account connection prerequisites, return values, error behavior, and guidance for most target platforms.

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%, so the description carries a heavy burden for explaining parameters. It does add genuine semantics for postMode, privacyLevel, and the segments arrays. However, it leaves the other platform target arrays (Instagram, Pinterest, LinkedIn, Facebook, Mastodon, Bluesky) without any explanatory guidance.

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 states a specific action (create) and resource (one scheduled item that publishes to social accounts), and clearly separates it from sibling tools like update_post, delete_post, and list_posts. The multi-account and scheduling scope adds specificity beyond the title.

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 provides explicit platform-specific usage instructions: TikTok requires choosing between DIRECT_POST and UPLOAD, with privacyLevel sourced from tiktok_get_creator_info, and X/Threads use ordered segments for threaded replies. It does not explicitly contrast with sibling creation-related tools, but the create-vs-update/delete distinction is self-evident.

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