delete_social_post

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

With no annotations, the description carries the full behavioral burden. It discloses which platforms support remote deletion and that Instagram/TikTok do not, which is valuable, but it never states that deletion is irreversible, what permissions are required, or how partial failure is handled when a platform-side delete fails.

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, no filler, with the core action stated first and the mode distinction second. Nothing could be removed without losing 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?

For a 2-parameter destructive tool with no annotations and no output schema, the description covers purpose and modes but says nothing about the result of the call (e.g., whether platform-specific failures are reported) or the irreversibility of the action. The schema is fully documented, so this is adequate but leaves a real gap around destructive semantics.

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 description coverage is 100%, so the schema already documents both postId and deleteFromPlatform in detail, including the Instagram/TikTok limitation. The description only restates the two modes at a higher level, adding no syntax or edge-case meaning beyond the schema, so baseline 3 applies.

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 gives a specific verb and resource ("Delete a post from SocialDispatch") and immediately clarifies the two deletion scopes, so the agent knows exactly what the tool does. It does not name or contrast with any sibling tool, but no sibling in the list performs deletion, so the ambiguity is low.

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 two modes (local-only vs. local-plus-platform) are described, which implies when each is appropriate, but there is no explicit "use this when..." framing, no prerequisites, and no exclusions or alternatives mentioned. The agent must infer that this is the terminal action after publish_social_post or schedule_social_post.

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