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

Adds real context beyond annotations: plan-tier entitlement for X, near-immediate publishing when scheduledAt is omitted, the requirement for explicit confirmation, and the TikTok eligibility gate. It does not restate irreversibility (that lives in the confirm schema field) but covers the non-obvious operational constraints well.

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-loads what the tool does, then stacks constraints in short declarative sentences with no filler. The plan-tier parenthetical is slightly dense but materially useful.

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 mutating, multi-platform publish tool with an output schema, this covers the key decision points an agent needs: platform eligibility, entitlement, timing semantics, confirmation, and the cross-tool dependency on list_social_accounts. Nothing essential to calling it correctly is missing.

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 100%, so the schema already documents title defaults, ISO 8601 format, READY status for clipId, and canPublishHere for socialAccountId. The description reinforces the omit-date behavior and TikTok gating but adds little syntax or edge-case detail the schema lacks; baseline 3 applies.

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 and resource (schedules a clip for publication) and enumerates the supported destination platforms (YouTube Shorts, Instagram Reels, X). It is clearly distinguishable from siblings like list_scheduled_posts or cancel_scheduled_post.

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 gating conditions: X requires a paid Pro/Elite plan, omitting scheduledAt publishes within a minute, and TikTok requires canPublishHere from list_social_accounts. It does not explicitly point to cancel_scheduled_post for reversal or list_scheduled_posts for verification, so the sibling routing is partial.

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