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

With destructiveHint=true already flagging danger, the description still adds real value by saying 'Permanently', clarifying irreversibility, and by stating the ownership requirement, which the annotation does not convey. It stops short of describing cascade effects, error behavior for non-owned posts, or what the response looks like.

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?

One short sentence, no waste, and the most consequential fact (permanent deletion) is front-loaded where the agent will read it first.

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 one-parameter destructive tool with no output schema, the description covers purpose, irreversibility, and ownership. Only minor gaps remain around failure modes (non-owned or missing post) and any side effects of removal.

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 one required parameter 'id' with 0% schema description coverage, but the description's reference to 'a post' makes clear enough that the id identifies the post to delete. That's the minimum viable explanation for a single obvious identifier, with no format or source-of-id detail added.

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?

Specific verb (delete) plus resource (post) plus ownership scope, and the adverb 'Permanently' disambiguates it from any soft-delete/archive behavior. Among siblings like create_post, update_post and retry_post, an agent can immediately tell this is the removal tool.

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 phrase 'a post you own' states a precondition, implying usage is restricted to owned posts, which is useful routing context. However, it never names an alternative (e.g., update_post to edit rather than remove) or explicitly warns when not to use it.

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