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

Adds substantial context beyond the annotations: the 'WILL publish publicly later' side effect, strict sequential ordering ('a part never goes out before the previous one'), the on-screen/caption text injected ('PART n/N'), the TikTok Inbox limitation, and the concrete idempotency mechanism (skip already-queued parts). This goes well past idempotentHint/destructiveHint and tells the agent exactly what happens on a second call.

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?

Front-loaded with the core action, then tightening constraints (ordering, idempotency, platform limit, publish warning) in descending priority. Four compact sentences, no filler or repetition of schema types.

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?

Covers timing, ordering, idempotency, side effects, and platform limits for a 4-param mutation with no output schema. The only minor gap is that it doesn't hint at the return value (e.g., which parts were queued vs skipped), though the skip behavior is described.

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 already 75%, but the description reinforces semantics: gapMinutes governs the spacing between parts, startAt is when Part 1 goes out, and the series is defined via seriesId pointing at a series=true request. It clarifies how parameters interrelate (ordering + cadence) rather than just restating types.

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?

Names a specific action (queue every part of a series) on a specific resource (a request created with series=true), in story order. It is clearly distinguishable from siblings like clipember_create_scheduled_post or clipember_reschedule_post because it explicitly scopes to multi-part series scheduling.

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?

Gives clear triggering context (a request with series=true, chosen platforms) and an important constraint (TikTok unsupported; already-queued parts are skipped). It doesn't name a specific alternative tool for single-post scheduling, but the series-vs-single distinction is stated explicitly, which is the key routing decision.

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