Delete a Threads post

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

The description goes far beyond the annotations. While annotations declare destructiveHint:true and readOnlyHint:false, the description explains the irreversibility, the two-step confirmation process, the purpose of confirmName, the 100-deletion daily quota, and the unknown effect on replies. It also notes the cost ('0 credits'). This is rich behavioral disclosure that adds substantial context beyond the structured annotations, and there is no contradiction.

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 long and dense, but every sentence contributes critical safety-critical information. It is front-loaded with the irreversible warning and the two-step workflow. While not concise in length, it is efficiently structured and avoids redundancy. Given the high-stakes nature of the operation, the length is justified, though it could potentially be tightened without losing essential guidance.

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?

The description covers the workflow, parameters, quota, and the ambiguity around replies, which is substantial. However, it does not explicitly describe the return format for the confirmed deletion call (beyond implying a success/failure). It does detail the unconfirmed call's response (post text, views, likes, etc.), but the confirmed call's output is left unspecified. Given the absence of an output schema, a bit more detail on the success response would improve completeness, but overall it's fairly complete for a destructive tool.

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?

Although schema coverage is 100%, the description adds significant meaning to the parameters. It explains that confirm must be true only after explicit user agreement, and it elaborates on confirmName's role as a safeguard to prevent blind deletion of the wrong post, specifying when it becomes required (after engagements). It also identifies postId as coming from list_threads_posts. This goes well beyond the schema's field descriptions, enhancing parameter understanding.

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 action: 'PERMANENTLY delete one of the brand’s Threads posts.' It uses a specific verb and resource, and the permanence is highlighted. Although it doesn't explicitly contrast with sibling delete tools for other platforms, the title and content unambiguously scope it to Threads, making it distinct from tools like delete_x_post or delete_bluesky_post.

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 provides detailed usage guidance: call without confirm to preview, then call again with confirm:true after user approval, and adds confirmName conditionally. It also explains the quota limit and mentions threads_publishing_limit. However, it does not explicitly say 'use this tool instead of delete_x_post for Threads,' but the platform-specific naming and sibling list make the appropriate context clear. The workflow is explicitly described, which is strong usage guidance.

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