ghl_create_social_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 mentions the core schedule/publish action, but omits important traits like immediate public posting, required permissions, reversibility, or what gets created. The schema's scheduledAt hint adds some behavior context, but the description itself is thin.

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 a single, front-loaded sentence with no filler. It conveys the core action and resource efficiently, earning its space.

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 simple 4-parameter tool with well-documented schema fields, the description is minimally viable. However, with no annotations and no output schema, it lacks return-value expectations, invocation prerequisites, and broader usage context, leaving notable gaps for an agent.

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 covers all 4 parameters with 100% description coverage, so the baseline is 3. The description adds little parameter-level meaning beyond the 'schedule or publish' framing; the schema already explains scheduledAt and the meaning of each field.

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 a specific action ('Schedule or publish') and clearly identifies the resource ('a social media post'), making the tool's purpose immediately understandable. It semantically distinguishes itself from sibling tools like ghl_get_social_posts and ghl_delete_social_post, though it doesn't explicitly name alternatives.

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?

There is no guidance on when to use this tool versus alternatives, no mention of prerequisites (e.g., retrieving account IDs via ghl_get_social_accounts), and no exclusions or limitations. The description simply states what it does without any contextual usage advice.

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