mixpost_create_post

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Create a new social media post' and fails to mention critical behaviors such as whether the post is immediately published, scheduled, or added to a queue, or how the 'schedule_now' and 'queue' parameters affect behavior. This is a significant transparency gap for a complex 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?

The description is extremely short (one sentence), which is concise but under-specified. It lacks any structural elements such as prerequisites, examples, or context. The brevity is not effective because it omits essential usage details, making it more of a title than a helpful description.

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 (9 parameters, no output schema, no annotations), the description is woefully incomplete. It does not explain the overall workflow, how accounts and versions interact, or the implications of scheduling and queue options. The description alone would not sufficiently guide an agent in selecting and invoking this tool correctly.

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?

The input schema provides descriptions for all 9 parameters, covering 100% of them. The tool description adds no additional parameter-level information beyond what the schema already contains. Since schema coverage is complete, the baseline score of 3 is appropriate; the description neither enhances nor detracts from parameter understanding.

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 uses the specific verb 'Create' and the resource 'social media post', clearly stating the tool's primary function. It differentiates from update/delete/list operations among siblings, though it does not explicitly distinguish from schedule_post or add_post_to_queue, which could also involve creating posts. Overall, the purpose is clear and unambiguous.

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 no guidance on when to use this tool versus alternatives. It does not mention whether to use it for immediate posting, scheduling, or queuing, nor does it reference any sibling tools. The single sentence is purely definitional and lacks any contextual usage instructions.

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