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

With no annotations, the description carries the full behavioral burden. It usefully discloses that deletion is scoped and does not touch already-published platform content, and it explains the interactive-panel rendering and the instruction not to echo its contents. It omits irreversibility, permission/auth requirements, and the fate of scheduled-but-unpublished posts.

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 core action and its scope are front-loaded in the first two sentences. The final clause about panel rendering is somewhat tangential to deletion but is short and actionable.

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 destructive tool with no annotations and no output schema, the description covers scope and UI rendering but leaves key gaps: whether the operation is irreversible, what permissions it needs, and how scheduled/published posts are affected.

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 single parameter postId has 0% schema description coverage and the description adds nothing about it, so the agent must infer it identifies the post to remove. The name is conventional enough that the gap is minor, but no meaning is added beyond the schema.

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 post") and clarifies scope with "Does not remove already-published content from the platforms." It does not, however, distinguish itself from the many sibling delete tools (delete_generation, delete_voice_clone) or from update_post/list_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?

There is no guidance on when to use this versus update_post, publish_post, or the other delete siblings, and no prerequisites or preconditions (e.g. must the post be unpublished first). The scoping sentence describes behavior, not usage conditions.

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