Bulk Delete Knowledge Bases

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

The description states 'Permanently delete' (destructive), but the annotation destructiveHint=false. This is a direct contradiction, and the description provides no additional behavioral context like error handling or partial failures.

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 concise sentence conveying action, target, scope, and permanence. No wasted words.

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 simple one-parameter bulk delete operation, the description is minimally sufficient but lacks details on return values, partial failure behavior, and prerequisites. The contradiction with annotations further reduces completeness.

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 only parameter 'config_ids' is fully described in the schema. The description adds no meaningful parameter detail beyond restating the operation.

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 verb 'delete' with resource 'knowledge base configs' and specifies 'multiple' and 'by id', clearly distinguishing it from single-delete siblings like lyzr_kb_delete.

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 word 'multiple' implies use for batch operations vs singular delete, but no explicit guidance on when to use vs alternatives or when not to use. It relies on the title and context.

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