Delete knowledge base item

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is fully covered by structured data. The word 'Permanently' reinforces irreversibility but adds little beyond destructiveHint, and nothing is said about the required audit reason, permissions, or failure behavior, so this is a baseline 3 with no contradiction.

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 filler, and the destructive qualifier is placed first. It is efficient, though the brevity doubles as under-specification for a destructive tool.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. Still missing for a permanent-delete tool: whether the audit reason is mandatory (schema says required, description does not warn), and what happens to the item's attachments or children.

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%: the required 'reason' parameter is documented as an audit-trail obligation with a minLength constraint, and 'knowbaseId' is typed. The description adds no syntax or format nuance, so the schema does all the work and 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?

The description gives a specific verb and resource ('Permanently delete a knowledge base article'), which is unambiguous and tells the agent exactly what object is affected. It does not, however, differentiate itself from same-family mutators such as glpi_delete_knowbase_category or glpi_delete_document_item beyond the resource noun.

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 statement of when to use this tool versus alternatives, no prerequisites, and no warning about when not to call it. The agent must infer that this is the terminal step after listing/getting an item, with nothing in the text to confirm that.

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