Delete social post

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=true, so the description does not need to restate that this is destructive. It adds useful scoping by limiting deletion to scheduled or draft posts, but 'Destructive' is redundant with the annotation and no additional behavioral detail is provided.

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 very short and front-loaded, stating the action and scope immediately. The standalone 'Destructive.' is redundant with the annotations and adds little value, but overall the description is appropriately sized.

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 delete tool, the required postId is clear, the scope is stated, and annotations cover the destructive and idempotent behavior. It does not describe return values or error behavior, but that is a minor gap for a delete operation.

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 schema already documents locationId, and postId is self-explanatory from the tool name. The description adds no parameter-level meaning, but with 50% schema coverage and the postId being intuitive, the lack of additional parameter detail is acceptable.

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 identifies the action 'Delete' and the resource 'social post', and further specifies 'scheduled or draft'. This makes it easy to distinguish from siblings like ghl_create_social_post, ghl_get_social_post, and ghl_list_social_posts.

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 phrase 'scheduled or draft' provides useful context about which posts this tool applies to, implicitly excluding published posts. However, it does not explicitly reference alternative tools or state when another tool should be used instead.

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