Delete Basic Post

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds useful context by stating it 'changes community state' and requires confirm=true, but it doesn't disclose whether deletion is permanent, whether it can be undone, or what permissions are needed.

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?

Two short sentences that are front-loaded with the action and its gating requirement; there is minimal waste, though the opening sentence merely restates the title.

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 destructive mutation tool with good annotation coverage and no output schema, the description is roughly adequate but thin. It omits permanence, reversibility, and permission requirements, and does not address what the post_id expects, so an agent has gaps for a state-changing operation.

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 67%: account and confirm carry descriptions while post_id does not. The description only echoes the confirm=true requirement already present in the schema, adding no format or semantic detail beyond what structured fields provide, so a baseline 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 names a specific verb (Delete) and resource (Basic Post), and the term 'Basic Post' hints at a distinction from the sibling delete_image_post. However it does not explicitly state how it differs from other post-mutation siblings like update_post or archive operations, leaving some differentiation to inference.

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; siblings such as delete_image_post, delete_comment, and update_post are never referenced. The only contextual cue is the confirm=true requirement, which gates the action but does not help the agent choose between tools.

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