Delete a post on X

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

The description goes beyond annotations. While destructiveHint=true already signals danger, the description explicitly states irreversibility ('CANNOT be undone'), instructs user confirmation, and discloses that credits are consumed. It also clarifies scope (connected account's posts) and the connection requirement, providing substantial behavioral context.

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 three sentences with no filler. It front-loads the most critical information (permanent deletion) and then provides necessary caveats (confirmation, credits, connection). Every sentence serves a purpose.

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 destructive action with one parameter, the description covers the essential elements: what it does, how to use it safely (confirmation), and prerequisites (connection, credits). It is sufficiently complete for an agent to invoke it correctly without additional details about response format.

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?

The single parameter 'id' is fully described in the schema with 'the numeric X post id — the last part of the post URL', and the tool description does not add additional meaning beyond what the schema provides. Since schema coverage is 100%, the baseline score of 3 is appropriate.

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 verb ('Permanently delete'), the resource ('one of the connected account’s posts on X'), and emphasizes the irreversible nature. This distinguishes it from sibling tools like edit_x_post, x_post_insights, or delete_bluesky_post by specifying the platform and scope.

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?

It gives explicit guidance to confirm the post with the user first, which is critical for a destructive action. It also notes prerequisites ('Needs X connected') and that credits are charged. However, it does not explicitly mention alternatives or when not to use it (e.g., when editing would suffice), though the platform-specific wording and context make it reasonably clear.

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