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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the danger profile is known. The description adds a genuine precondition not present in structured fields: the platform support matrix that will cause the call to fail on Instagram and TikTok. It still omits failure modes such as deleting an already-deleted post or what happens to the underlying posting log entry.

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 short sentences with the core action front-loaded and the platform constraints following immediately. Every sentence carries information an agent needs; there is no repetition of the tool name or schema content.

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 two-parameter destructive mutation with a fully described schema, full annotation coverage and no output schema, the definition covers action, scope and platform eligibility. The only meaningful gap is behavior on edge cases like already-deleted or partially failed posts, which would matter for error recovery.

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%, with both launch_id and posting_log_id documented (the latter noting it comes from launch status). The description adds no further meaning about these identifiers, so the schema carries the full burden and the baseline of 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?

States a specific verb and resource ('Delete a single published post from its platform') and the word 'single' implicitly distinguishes it from the sibling bulk tool delete_all_posts. An agent can tell exactly what this does and at what granularity without opening the schema.

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?

Gives clear eligibility context by enumerating supported platforms (Twitter, Facebook, LinkedIn, Reddit, YouTube) and ruling out Instagram and TikTok due to API limits, which directly determines when this call will succeed. It does not explicitly route the agent to delete_all_posts or discuss what to do when unsupported platforms are involved, so it stops short of full alternative guidance.

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