Delete a post from the connected Bluesky account

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

The description goes well beyond the destructiveHint annotation by detailing the irreversibility ('no trash and no undelete'), the cascade deletion of likes/reposts/replies/quotes, and the rationale for confirmText as a safety mechanism. It also discloses credit cost and the connection prerequisite, which are not in annotations.

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 but every sentence serves a purpose for a destructive operation. It front-loads the critical warning ('PERMANENTLY delete') and then flows logically through the confirmation process, ID formats, and constraints. Some redundancy could be trimmed, but the density is justified.

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 identification via AT-URI or record key, the two-step confirmation flow, when confirmText is necessary, ownership restrictions, credit cost, and connectivity requirement. For a complex destructive tool with no output schema, nothing an agent needs to call it correctly is missing.

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 descriptions cover all three parameters, but the tool description adds practical guidance: the 40-character threshold for confirmText, the alternative record-key format, and the note that confirm is 'REQUIRED true'. This enriches the schema's bare definitions.

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 opens with 'PERMANENTLY delete one of the connected Bluesky account's OWN posts', stating a specific verb, resource, and ownership constraint. It immediately distinguishes this tool from other platform-specific deletes (delete_x_post, delete_telegram_message, etc.) by referencing the connected account and Bluesky platform.

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 an explicit two-step workflow: call without confirm first to preview, then call with confirm:true after user approval. It also specifies when confirmText is required (once the post has any engagement). However, it does not explicitly name alternative tools for other platforms, though the platform-specific scope makes the intended use case clear.

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