create_post

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

With no annotations, the description carries the full burden. It discloses scheduling behavior, per-channel inheritance, and platform-specific settings (e.g., privacy_status, made_for_kids). It could mention idempotency or failure handling, but overall provides good transparency.

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 description is well-structured with a clear first sentence stating purpose, followed by scheduling mode explanation, then per-channel settings, then platform specifics. It is somewhat long but each part adds value. Could be slightly more concise.

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?

Given the tool's complexity (6 parameters, 4 required, platform-specific settings) and no output schema, the description is thorough. It covers all key aspects: scheduling, inheritance, constraints, and channel-specific configurations.

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 50%, but the description adds significant meaning beyond the schema. It explains schedule_mode values, per-channel settings inherit from title/body, and details YouTube and TikTok-specific parameters, which are not described in the schema.

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 clearly states the tool creates and schedules a video post across one or more channels, with specific verbs and resource. It distinguishes from siblings like list_posts, get_post_metrics, etc., which are read-only or status-checking tools.

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 explains both schedule modes ('queue' vs 'custom') and their behavior, and mentions a constraint (brand_content_toggle cannot combine with SELF_ONLY). However, it does not explicitly state when not to use this tool or suggest alternatives for different use cases.

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