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

Goes well beyond the annotations: it enumerates exactly what is destroyed (platform-specific records and media), discloses the 409 protection conditions for published/uncertain/in-flight content, and draws the boundary that posts are not removed from social networks. That is meaningful operational context that destructiveHint/idempotentHint alone do not convey.

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 tight sentences, front-loading the action and scope, then the failure conditions, then the scope boundary. No filler and every clause carries 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 single-parameter destructive tool with no output schema, the description covers the action, its cascade effects, its failure mode, and its limits. Nothing an agent needs to invoke it correctly is missing.

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?

There is only one parameter (postGroupId) and schema description coverage is 100%, so the schema already carries the parameter semantics. The description adds no format, ID-source, or lookup guidance beyond what the schema provides — baseline 3.

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 precise verb (delete) and a precisely-scoped resource (an unpublished post group plus its platform-specific records and media), which cleanly separates it from siblings like delete_media or update_post. The scope qualifier 'unpublished' is stated up front rather than buried.

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 an explicit when-not: published, partially published, uncertain publish outcomes, and in-progress publishing are protected and return HTTP 409, so the agent knows when this call will fail. It does not, however, name an alternative tool for handling published content, so the routing guidance is incomplete.

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