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 structurally. The description's addition of "Cannot be undone" genuinely confirms permanence — information a hint alone doesn't convey — but it stops there: nothing about required permissions, what happens to dependent records (e.g. comments on a deleted entry), or whether the confirm flag can be bypassed programmatically.

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 sentences, no filler, with scope stated first and the irreversibility warning front-loaded at the end where it lands hardest. Nothing repeats the title or the schema.

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 six-parameter destructive tool with full schema coverage and no output schema, the description covers what is deleted, from where, and that it's permanent. The remaining gaps — the user-approval gate for confirm, the forum exclusion, and the module/polls alias — are all handled in the schema, so nothing critical is missing, though a one-line cross-reference to content_write would have made it 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 description coverage is 100% and the action enum's oneOf entries already spell out per-action required parameters (id vs channel_id vs filter_num). The description adds no format or behavioral detail beyond the resource vocabulary that maps loosely to the action values, so it sits at the baseline rather than adding value.

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 (deletes) plus the exact resource set (entries, categories, comments, filters, video channels) and scopes it to a content module of the active site. An agent immediately knows what this destroys, though the description itself does not differentiate it from the sibling content_write or point to forum_delete for forum content — that distinction only appears in the schema's module field.

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 choose this tool over content_write or the module-specific *_delete siblings, and no mention of prerequisites such as selecting a site first. The only directional statement is a consequence ("Cannot be undone"), which warns but does not route.

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