Create Social Media Post

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

Annotations already indicate readOnlyHint=false, so the agent knows this is a write operation. The description adds the 'schedule or publish' nuance, which clarifies immediate vs. delayed execution. However, it doesn't disclose other behavioral details like idempotency, rate limits, or required permissions, but annotations cover the primary safety profile.

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, efficient sentence that clearly communicates the core action without redundant information. It front-loads the purpose and avoids any unnecessary elaboration.

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 is relatively simple with 5 parameters and no output schema. The schema descriptions cover most parameter semantics, and annotations provide safety context. The description, while minimal, combined with the schema and annotations gives a complete picture for an agent to invoke this tool correctly. A minor gap is not explaining what the response contains, but for a create/schedule operation this is typically not essential.

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 80%, so most parameters have descriptions. The description itself adds no additional parameter semantics beyond the schema. The 'scheduledDate' parameter already has a clear description ('omit for immediate publish') in the schema, and the description doesn't enhance it further.

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 verb ('Schedule or publish') and a clear resource ('social media post'), making it obvious this is a creation/scheduling action. It distinguishes itself from sibling list tools like ghl_list_social_posts and ghl_list_social_accounts by indicating it performs a write operation.

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 clearly implies when to use this tool (to create or schedule a post) versus listing posts, but it does not explicitly state alternatives or exclusions. There's no guidance on when to choose this over other creation tools, though the resource is unambiguous.

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