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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered; the description adds two pieces of non-structured context: the authorization requirement ('needs bearer token with scope: post') and the ownership restriction on what can be deleted. It stops short of saying whether deletion is reversible or what happens to replies.

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 short sentences; the action and its scope come first, with the auth prerequisite in a compact bracket. Nothing is padded and nothing needs reordering.

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 no output schema, the definition covers purpose, ownership constraint, and auth scope, which is most of what an agent needs. Remaining gaps (irreversibility, effects on dependent content, channel format) are minor given the annotations already flag the destructive nature.

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% and the two parameters are documented in the schema, but their descriptions are only the bare words 'channel' and 'post id'. The description adds no format, identifier, or lookup guidance beyond what the schema already provides, so the 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?

States a specific verb and resource ('Delete one of your own posts') and adds an ownership constraint that narrows the scope. No sibling tool performs deletion, so distinguishing from alternatives is largely moot, but the definition never explicitly contrasts itself with post/react/report.

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 'one of your own posts' phrasing implies the usage condition (you can only remove content you authored), but there is no explicit when-to-use or when-not-to-use guidance, and no alternative tool is named for adjacent operations such as editing or moderating content.

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