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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description's parenthetical '(soft delete)' adds genuinely new context the annotations do not provide: the record is not permanently removed, which materially changes how an agent should reason about reversibility.

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 front-loaded sentence with zero waste. The most decision-relevant qualifier, soft delete, is placed immediately after the verb.

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 annotation coverage and no output schema, most of what an agent needs is present via annotations plus the soft-delete note. Missing is whether deleted knowledge bases can be restored and through what tool, and what effect deletion has on contained articles or comments, which matters for a destructive operation on a container resource.

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?

Only one parameter, and the schema documents it at 100% coverage ('Knowledge base ID'). The description adds nothing about the parameter, so the schema carries the full load; 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?

States a specific verb (delete) and resource (knowledge base), so the action is unambiguous and matches the name and title. It does not explicitly differentiate itself from siblings like delete_article or delete_category, but the resource in the name does that implicitly.

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 use this versus alternatives such as update_knowledge_base or a future restore/hard-delete path, and no prerequisites or warnings about consequences. The agent must infer everything from the name alone.

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