x_delete_post

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly states 'Cannot be undone,' highlighting the irreversible destructive nature, and restricts to 'your own posts,' implying an ownership/permission constraint. It does not mention authentication, rate limits, or side effects, but for a simple delete it covers the most critical behavioral traits.

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 two short sentences with zero filler. The core action is front-loaded, and the critical caveat about irreversibility is stated concisely. Every word earns its place.

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 simple one-parameter destructive tool without an output schema, the description covers the essential context: what it does, the ownership scope, and the permanence of the action. It omits the success/response format, but this is a minor gap given the tool's simplicity. The required parameter is documented in the schema, so the description need not repeat it.

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 0%, so the description must compensate, but it does not mention the post_id parameter or how to specify which post to delete. The schema's parameter name and type provide minimal information, yet the description adds no semantic context beyond the tool's general purpose. This leaves the agent to infer that post_id identifies the target post.

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 states a specific verb and resource: 'Delete one of your own posts.' It also scopes the action to 'your own posts,' which clearly distinguishes it from siblings like x_create_post, x_get_post, and x_search_posts. The action is unambiguous and immediately understandable.

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 implies usage: use this tool when you want to delete a post that you own. However, it does not explicitly state when not to use it, nor does it mention alternatives among the sibling tools. The guidance is reasonable but entirely implicit.

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