Create social post

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

Annotations indicate readOnlyHint=false (write operation) and idempotentHint=false (may create duplicates), which the description aligns with by stating 'Schedule or publish'. The description adds useful behavioral context: the scheduleDate behavior (omit for draft) and that mediaUrls must already be hosted in GHL. However, it doesn't disclose what happens on validation failure (e.g., invalid accountIds) or whether scheduling requires future dates only. The openWorldHint=true suggests the API may have side effects not fully enumerated, a subtle discrepancy not contradicted.

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?

Two sentences with zero redundancy. Front-loads the core action, then clarifies scheduleDate and mediaUrls in the second sentence. Efficient use of words – each phrase adds information.

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?

The tool has 6 parameters, 2 required, no output schema, and write semantics. The description covers the key scheduling/drafting logic and media prerequisites. However, it doesn't explain the status parameter's full interaction (e.g., what happens when status='published' with no scheduleDate – immediate publish?), nor does it mention account lookups or validation behavior. An agent might need to infer that status='scheduled' requires scheduleDate, and status='published' publishes immediately. The schema provides the enum but not the semantic rules. The description could be more complete here but isn't critically deficient.

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 83% (5 of 6 properties have descriptions), so the description adds marginal value. However, it clarifies the critical semantics of scheduleDate ('ISO 8601 time to publish. Omit to create as draft.') which is slightly different from the schema's 'Omit to create as draft.' The description also clarifies that mediaUrls must already be hosted, adding context beyond the schema's 'URLs of media to attach.' The status parameter's interaction with scheduleDate is implied but not fully explained in the description. Given the high schema coverage, the description adds meaningful but not essential clarifications.

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 action ('Schedule or publish a social post to one or more connected accounts') with a specific verb and resource. It differentiates from siblings like ghl_list_social_posts, ghl_get_social_post, and ghl_delete_social_post by focusing on creation/scheduling. The distinction between scheduling and immediate publishing is explicit.

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 clear context on when to use scheduleDate (for scheduled posts) and mentions that omitting scheduleDate creates a draft based on status. However, it does not explicitly state when NOT to use this tool versus alternatives like ghl_list_social_posts or ghl_upload_media_by_url. It also doesn't mention prerequisites like needing connected accounts or how to find accountIds (though ghl_list_social_accounts exists as a sibling).

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