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

Annotations indicate a write operation (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds behavioral context: it explains TikTok's two publish modes (DIRECT_POST vs UPLOAD) and thread chaining for X/Threads, which is beyond the schema. It does not contradict annotations and provides useful operational details.

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 concise and front-loaded with the primary purpose, then dives into platform-specific details. It is well-structured with clear sentences, though it packs a lot of information into a short space. No wasted words, but could be slightly more organized for readability.

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 extremely large and complex input schema (10 top-level parameters, each with deep nesting) and no output schema, the description is insufficient. It does not explain many platform-specific fields (e.g., Facebook, LinkedIn, Pinterest, Instagram variants), return values, error handling, or scheduling behavior. The description covers only a fraction of what an agent needs to correctly invoke this tool.

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 0%, so the description must compensate. It explains postMode, privacyLevel (indirectly), and segments, but many other parameters (e.g., scheduledFor variants, media transforms, commercial content) are not described. The description adds some value but leaves many parameters unexplained given the tool's complexity.

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 creates a scheduled item that can publish to multiple social accounts, with specific platform details (TikTok modes, X/Threads threads). It distinguishes itself from sibling tools like update_post and delete_post by focusing on creation and scheduling. The verb 'create' and resource 'scheduled item' are specific and unambiguous.

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 concrete usage guidance for TikTok (postMode and privacyLevel), X and Threads (segments for threads). It implies when to use this tool (to create a post) but does not explicitly state when not to use it or mention alternatives like update_post. The guidance is clear for the key scenarios but lacks explicit exclusions.

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