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

Annotations already declare destructiveHint=true and idempotentHint=true, so safety and repeat-call behavior are covered structurally. The description does add real value by disclosing that the deletion is a soft delete (i.e., not a hard purge), but it omits side effects on comments, tags, and versions, and whether/how the article can be restored.

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?

A single short clause with the key qualifier front-loaded and zero filler. It is arguably under-specified rather than padded, so it scores well on conciseness but not on richness.

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 one-parameter destructive tool with full schema coverage and annotations declaring destructiveness and idempotency, the description covers the essentials plus the soft-delete nuance. Missing restore/cascade details are a modest gap given annotations do much of the work.

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 a single parameter at 100% schema description coverage, the schema already carries the parameter semantics. The description adds nothing about articleId format (UUID vs slug) or behavior on an unknown/nonexistent ID, so the baseline 3 applies.

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?

Names a specific verb and resource ("Delete an article") and adds a qualifier ("soft delete") that distinguishes the operation's nature. Resource naming separates it from delete_comment/delete_category/delete_knowledge_base siblings, though it does not explicitly contrast with restore_article_version.

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?

No guidance on when to use this versus alternatives such as restore_article_version, nor any stated preconditions (permissions, published vs draft state). The agent must infer everything about applicability from the tool name alone.

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