knowledge_base_delete_knowledge_base

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description's 'Delete a knowledge base' is consistent but adds no behavioral context beyond what annotations provide. It does not mention irreversibility, impact on associated data, or any side effects.

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?

The description is a single, clear sentence with no fluff or redundancy. It is front-loaded and to the point. However, the extreme brevity means it omits crucial details, but conciseness itself is high.

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?

Given that this is a destructive operation with a single parameter and no output schema, the description is incomplete. It lacks any explanation of the parameter, how to identify the knowledge base, or the consequences of deletion beyond what annotations imply. The agent has insufficient information to call this tool correctly without external knowledge.

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?

The input schema has 0% description coverage for the knowledgeBaseId parameter, and the description provides no explanation of what this parameter represents, how to obtain it, or its format. The agent is left to infer that knowledgeBaseId identifies the knowledge base to delete, but no details are given.

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 clearly states the action (delete) and the resource (a knowledge base). It is specific and unambiguous, and the name reinforces it. However, it does not differentiate from sibling tools like knowledge_base_delete, which could cause confusion about which delete operation to use.

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?

No guidance is provided on when to use this tool versus alternatives, no prerequisites, and no conditions. The description is purely a statement of action with no context on how it fits into a workflow.

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