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

Annotations declare non-read-only, open-world, non-idempotent behavior; the description adds timing semantics ('without a date, the post goes out within a minute'), a mandatory confirmation gate, and plan-based authorization limits, none of which the annotations express. Irreversibility is stated but largely duplicated from the confirm parameter's schema text.

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?

Four tight sentences with no filler, leading with what the tool does and the platforms it targets. The closing TikTok sentence is slightly tangential but still earns its place as an explicit exclusion.

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?

With an output schema present, return values need no explanation, and the annotations cover the safety profile. The description completes the picture with plan gating, confirmation requirement, and scheduling-vs-immediate behavior; only the prerequisite that the clip be READY is left to the schema.

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 100%, so all six parameters are already documented, including scheduledAt's ISO 8601 format and confirm's boolean requirement. The description only reinforces the omitted-date behavior, which the schema already states, so it adds little beyond the structured fields.

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?

States a specific verb (schedules) plus resource (a clip) and the exact destinations (YouTube Shorts, Instagram Reels, X), which cleanly separates it from siblings like list_scheduled_posts and cancel_scheduled_post. An agent can identify the operation and its scope 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?

Gives concrete usage conditions: X requires a paid Pro/Elite plan (explicitly ruling out Free, Creator, trial, gifted), omitting a date means near-immediate publication, and TikTok is handled elsewhere ('published from the app'). It does not name sibling alternatives directly, but the platform exclusions and plan gating provide real routing guidance.

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