create_post

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

With no annotations, the description must disclose behavioral traits itself. It mentions scheduling and immediate publishing (a mutation) but does not discuss irreversibility, authentication requirements, failure handling, or what happens after publishing. This is a notable gap 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?

The description is one concise sentence, front-loaded with the core action 'Schedule or publish immediately.' Every word contributes meaning, and there is no redundant or filler content.

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?

Despite the schema covering parameter details, the tool has no annotations or output schema, leaving the description as the only source for behavioral context. It fails to mention expected return values, error conditions, or platform-specific constraints, which is inadequate for a 7-parameter mutation tool.

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?

All 7 parameters have schema descriptions (100% coverage), so the schema does the heavy lifting. The description adds no new semantic detail beyond the schema; it echoes the notion of platforms and accounts but does not clarify any parameter beyond what's already provided.

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 specific verbs 'Schedule or publish immediately' and identifies the resource 'a post to one or more social media platforms or specific accounts,' clearly distinguishing its dual publishing modes. However, it does not explicitly contrast with sibling tool publish_post_now, so it falls short of a 5.

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?

No explicit guidance is provided about when to use create_post over alternatives like publish_post_now or update_post. The description implies scheduling or immediate publishing but gives no exclusions, prerequisites, or alternative scenarios, leaving usage context unclear.

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