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

Annotations already declare destructiveHint/idempotentHint, but the description adds real value beyond them: deletion cascades to a post's comments, there is no trash so it is irreversible, a per-call confirmation is on by default and can be switched off, and the call blocks on owner approval. That is exactly the behavioral context an agent needs before a destructive write.

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?

Irreversibility is stated three times ('for good', 'Skool keeps no trash', 'cannot be undone'), and 'as Skool's Delete does' plus the trailing 'Waits for the owner's approval' are ambiguous filler. The key scope and permission facts are front-loaded, but the sentences do not all earn their place.

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 parameter-light destructive tool with no output schema, it covers permissions, cascade behavior, irreversibility, and the confirmation flow. It omits secondary effects (e.g. what happens to likes, notifications, or the parent post when a comment is deleted), which keeps it from being fully complete.

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 coverage is 100%, so both parameters are already documented, and the description's 'pass its comment_id' mostly restates the schema's note that post_id may be a comment_id. Slight friction: it says to pass 'comment_id' while the only parameter is named post_id, which could confuse argument construction. 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?

States a specific verb and resource ('Delete a post or a comment') and immediately distinguishes the two modes: a whole post with its comments, or a single comment. It also separates itself from the many other delete_* siblings by naming the exact object type it removes.

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?

Gives clear usage context: your own posts/comments always, anyone's only when you are a group admin or moderator. It also explains the comment-deletion path. It does not name alternatives (e.g. update_post to edit instead of delete), so it stops short of full routing guidance.

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