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

Annotations already signal that this is destructive and not read-only; the description adds a useful guardrail by stating that published posts cannot be deleted. It doesn't describe side effects, soft-delete behavior, or error handling, but the annotation plus limitation is enough for a modest score.

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 description is only two sentences, with no filler. The main action is front-loaded, and the crucial constraint about published posts immediately follows.

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 operation with an output schema present, the description covers the what, the required parameter, and the primary state restriction. No extra information about return values is necessary because the output schema exists, and the destructive behavior is already annotated.

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?

Input schema coverage is 100%, and the schema already describes post_id as 'The post ID to delete (required).' The description's usage of 'by ID' adds no new semantics, so it rests at 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?

The description clearly states the tool's action ('delete a post') and the ID-based targeting, which is specific enough to distinguish from post-creation, listing, and editing tools. However, it does not explicitly contrast with the related sibling posts_unpublish_post, so the differentiation is not maximally explicit.

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 description conveys an important limitation: 'Published posts cannot be deleted,' which implicitly tells an agent when not to use this tool. It does not identify alternative workflows or sibling tools (e.g., unpublishing first), so usage guidance remains implied rather than fully explicit.

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