posts_delete

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

With no annotations, the description carries the full burden, and it does disclose the most important behavioral trait: the delete is permanent and irreversible. However, it omits auth/permission requirements, whether related data (comments, tags) is cascaded, and any error behavior, leaving substantial gaps for a destructive operation.

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 with zero filler; the destructive action is front-loaded and the irreversibility caveat follows immediately. Nothing needs trimming.

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 core information (what it deletes, that it is permanent) is present. Minor omissions remain around permissions and side effects, but an agent has enough to invoke it correctly.

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?

Only one parameter exists and schema description coverage is 0%, so the description must compensate. Saying 'by id' confirms the identifier's role, but adds nothing about acceptable format (slug vs numeric vs UUID) or validation, so the gap is only partially closed.

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 (delete) and resource (post) plus the scoping key (id), which cleanly separates it from posts_browse, posts_read, and posts_update. It does not explicitly name a sibling or contrast itself with pages_delete, so it stops just short of a 5.

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 when-to-use guidance and no alternative named (e.g., posts_update for edits). The irreversibility warning implies caution, but the description never states under what conditions this tool should be chosen over modifying or archiving a post.

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