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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered; the description adds the irreversibility detail ('Cannot be undone'), which is real value. However, it omits important behavioral facts such as whether deleting a forum cascades to its topics/posts, and that confirm must be true only after user approval — that lives only in the schema.

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, front-loaded with the scope of deletion and immediately followed by the irreversibility warning. Nothing is wasted or buried.

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 an 8-parameter destructive tool with no output schema, the description is adequate but thin: it says what gets deleted and that it is permanent, while the cascade behavior and the human-approval requirement are left to the schema. An agent reading only the description would have an incomplete model of consequences.

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 100%, and the oneOf entries already explain per-action id requirements and the confirm flag, so the schema does the heavy lifting. The description's list of entity types loosely mirrors the five actions but adds no id-format or precedence detail beyond what the schema states.

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 gives a specific verb ('Deletes') and enumerates the exact resource types covered (forums, sections, topics, posts, polls), which maps cleanly onto the action enum. It is clearly distinguishable from sibling forum_read and forum_write by its destructive scope, though it never names those siblings explicitly.

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?

Usage is only implied: the enumeration of entity types plus 'Cannot be undone' signals a destructive operation to be used deliberately. There is no explicit guidance about when to choose this over forum_write, nor any mention of the approval/confirm workflow that the schema requires.

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