create_post

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

With no annotations provided, the description must disclose behavioral traits. It covers the publish-schedule-draft flow but omits critical details such as what happens on partial failure, rate limits, required permissions, or response structure. The absence of error or return information limits 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 four sentences with no redundancy. It front-loads the core purpose, then logically proceeds to scheduling options, then shortcuts. Every sentence adds unique value, making it easy to parse quickly.

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 complexity (8 parameters, nested objects, no output schema), the description should cover what the tool returns (e.g., post ID, status). It omits this, leaving the agent unsure of the response format. However, it adequately covers the main use cases and references related tools (upload_media, list_social_accounts). Completeness is adequate but not strong.

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%, but the description adds significant semantic value beyond the schema. It explains the interplay between scheduled_at and status, describes platform_configurations as per-network tweaks, and clarifies that account_configurations are finer-grained than platform_configurations. This enables correct parameter use more effectively than schema alone.

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 'Create a social post across one or more connected accounts/platforms' and labels it 'the primary publishing tool.' This distinguishes it from sibling tools like create_draft, publish_now, and schedule_post, which are explicitly mentioned as simpler alternatives for common cases.

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 provides explicit guidance on when to use this tool versus shortcuts ('For common cases the shortcuts publish_now / schedule_post / create_draft are simpler'). It also explains how to configure immediate publish, scheduling, or draft mode using scheduled_at and status fields.

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