moltbook_delete_post

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

With no annotations provided, the description carries the full behavioral disclosure burden. It implies a destructive write operation but doesn't state whether deletion is permanent, whether it requires ownership, what happens to associated comments, or what the response looks like. This is a significant gap for a mutation tool.

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 a single, front-loaded sentence with zero waste. It delivers the core information immediately and is appropriately sized for a simple deletion tool.

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?

Given no annotations, no output schema, and a destructive operation, the description is incomplete. It should disclose permanence, error conditions (e.g., invalid ID, not owner), and any side effects. For a mutation tool, this is inadequate.

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 input schema has 100% coverage with a clear description for postId ('The ID of the post to delete'), so the schema does the heavy lifting. The tool description adds no additional parameter semantics beyond what is already in the schema. Baseline 3 is appropriate when schema coverage is high.

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 (delete) and resource (your own posts) with a clear scope constraint (own posts only). It distinguishes itself from siblings like moltbook_post (create) and moltbook_comment by targeting post deletion. However, it doesn't explicitly name alternative tools or differentiate from other deletion-like operations.

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 guidance on when to use this tool versus alternatives such as if you want to delete a comment versus a post, or whether moderation tools exist. The only implied usage is 'delete one of your own posts,' which is minimal context. No exclusions or prerequisites are stated.

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