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

Annotations only cover the generic safety profile (readOnly=false, destructive=false, openWorld=true, idempotent=false). The description adds genuinely non-derivable behavior: YouTube Shorts/Instagram Reels post publicly and irreversibly, TikTok only uploads and requires an in-app Inbox notification step by the user, and the account must already be connected. That is exactly the context an agent cannot get from structured fields.

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 the critical public-posting warning is front-loaded right after the purpose sentence, and every sentence carries actionable content. It is on the long side (five sentences, including the TikTok notification walkthrough), but that length is driven by real platform divergence rather than filler.

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 mutation tool with no output schema, the description covers the hazards, prerequisites, and per-platform outcomes well. What it omits is failure/duplicate handling — with idempotentHint=false, an agent isn't told whether a retry or repeated call double-posts, and no return value (e.g., a scheduled post id) is hinted at.

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 low (33%), with only scheduledFor documented in the schema. The description compensates well: it explains scheduledFor semantics ('right now or a few seconds out' means act immediately) and gives rich meaning to the platform enum values. clipId remains unexplained beyond the implied 'rendered clip', which is the one gap preventing a 5.

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 first sentence states a specific verb (queue), resource (rendered clip), and effect (publish to a platform at a given time). It is immediately distinguishable from siblings like clipember_reschedule_post, clipember_retry_failed_post, and clipember_create_clip_request.

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?

It gives explicit when-to-use guidance (confirm with the user before public YouTube/Instagram posting), an alternative pattern (pass scheduledFor of right now to act immediately), and a prerequisite with the exact sibling to check (platform must be connected — clipember_list_platform_connections). Per-platform behavioral branching is spelled out rather than implied.

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