Delete Knowledge Base

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

Annotations already mark this as destructive and not read-only; the description adds the key detail that deletion is 'permanent', signaling irreversibility. This goes beyond the annotations and sets correct expectations, though it does not mention cascading effects or required permissions.

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?

One short sentence, 'Permanently delete a knowledge base by id.' Front-loaded with the verb, and every word contributes meaning without redundancy.

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 single-parameter delete tool with strong annotations, the description covers the core action and irreversibility. It lacks details on return value or consequences, but output schema is absent and the operation is simple enough that this is a minor gap.

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 coverage is 100% with kb_id described as 'Knowledge base id'. The description's 'by id' adds no new semantics beyond the schema, so the baseline of 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 uses the specific verb 'delete' and names the resource 'knowledge base' with 'by id' scope. This clearly distinguishes the tool from siblings like lyzr_kb_bulk_delete, lyzr_kb_delete_docs, and lyzr_kb_reset.

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?

The description implies the tool is for deleting a single knowledge base identified by kb_id, but it does not explicitly state when to use it versus alternatives such as bulk delete or document deletion. No exclusions or alternative tool references are provided.

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