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

Annotations already flag destructiveHint=true, so the bar is lower, yet the description adds real context: the two-phase confirm gate ('previews until confirm: true') and the permission model for whose posts can be removed. It stops short of saying whether comments/reactions are cascaded or the deletion is irreversible.

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 compact clauses, front-loaded with the verb and resource before the permission and confirm caveats. Nothing is padded and every phrase carries information.

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 single-parameter mutation with annotations covering the safety profile and no output schema, the description covers the essential operational facts: permission scope and the preview/execute gate. Only the blast radius (child comments, reversibility, error-on-missing) is unaddressed.

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?

With 2 parameters at 50% schema coverage, the schema already documents 'confirm' thoroughly, and the description merely echoes that preview/execute split. 'postId' is left entirely to the schema, so the description neither compensates for the coverage gap nor adds format/identifier guidance.

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?

States a specific verb+resource ('Delete a community post') and adds the authorization scope (own post, or any if moderating). It does not explicitly distinguish itself from the close sibling delete_community_comment, but the resource noun 'post' plus the ownership clause makes selection unambiguous in practice.

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 ownership/moderation clause effectively states when the call is permitted, which is useful precondition guidance. However there is no explicit when-to-use-vs-alternative routing (e.g., use delete_community_comment for replies), and no note on what to do if the post isn't yours.

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