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

No annotations are present, so the description carries the full disclosure burden. It usefully discloses the token requirement and the dual create/update semantics, but it does not mention that the publish parameter can take a draft live, nor how an update overwrites existing content — both consequential behaviors for a mutation tool.

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?

Two sentences, each earning its place: the first summarizes purpose and content shape, and the second states the authentication requirement. It is dense but not bloated, and the purpose is front-loaded.

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 21-parameter creation tool with zero annotations and zero schema descriptions, this description is incomplete. The update-vs-create trigger, the redundancy of channel_title/channel_url alongside channel_slug, and the publish flag's side effects are all left to inference. The output schema mitigates only return-value questions, not invocation semantics.

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 0%, so the description must compensate, but it names only the headline content fields (SEO title, keywords, tags, source URL, text/video blocks). The six required parameters (coach_slug, channel_slug, channel_title, channel_url, source_post_url, write_token) and the remaining optional fields such as slug, excerpt, language_code, and source_platform are left unexplained in both schema and description.

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 states a clear verb+resource ('Create or update a trainer social post') and enumerates the content payload (SEO title, description, keywords, tags, source URL, ordered text/video blocks). The name 'draft' plus the sibling publish_social_post imply a drafting stage, but the description does not explicitly differentiate itself from siblings.

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 gives no guidance on when to use this tool versus siblings such as publish_social_post, upsert_social_channel, or list_social_posts. The only prerequisite mentioned is the write token, so an agent gets no selection cues and no exclusions.

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