ghl_social_delete_current_active_post_and_schedule_next

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

Annotations include destructiveHint=true, making the destructive behavior explicit. The description adds the auto-scheduling behavior and endpoint details (OAuth scopes, version). No contradictions, but could disclose more about failure scenarios or queue empty case.

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?

Three sentences: one states purpose, one explains behavior, one gives endpoint and scopes. No fluff, but the endpoint info could be better integrated. Front-loaded with the action.

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?

No output schema and description does not explain response behavior, error handling, or how to get the required postId. For a tool that both deletes and schedules, more detail is needed.

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?

50% schema coverage: locationId has a description, postId does not. The description only mentions postId in the endpoint path but does not explain its meaning or how to obtain it. Schema already documents locationId, so value added is minimal.

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 tool name and description clearly state the action (delete active post) and secondary action (schedule next). It distinguishes from siblings like ghl_social_delete_post which only deletes without scheduling.

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 explains the tool's effect (delete scheduled active post and auto-trigger next scheduling). It implies context but lacks explicit when-not or alternative tool guidance. Given siblings that handle other deletion scenarios, the context is clear enough.

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