bulk_delete_knowledge_bases

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states 'delete multiple knowledge bases at once' without mentioning irreversibility, error handling (e.g., partial failures), permissions required, or impact on associated data.

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?

Two concise sentences with no wasted words; front-loaded with the core action and followed by a clear usage context.

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 destructive batch operation, the description lacks critical context: no warning about potential data loss, limits on batch size, behavior on invalid names, or confirmation steps. It is inadequate for safe and correct usage.

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 documentation coverage is 100% (the only parameter 'kb_names' is described as 'Array of knowledge base names to delete'). The description adds no additional meaning beyond the schema, so 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 explicitly states the verb 'Delete', the object 'multiple knowledge bases', and the scope 'at once. Useful for batch cleanup operations.' This clearly distinguishes it from the sibling single-delete tool 'delete_knowledge_base'.

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 suggests batch cleanup as a use case, implying when to use it over individual deletes. However, it does not provide when-not-to-use guidance or mention prerequisites, limits, or risks.

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