delete_kb_documents

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It merely states the action without revealing destructive nature, irreversibility, or potential errors. An agent cannot infer side effects or safety implications from this description.

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 concise sentence, which is appropriate in length and front-loaded. However, it is almost unnecessarily terse, with no additional context, but it doesn't waste words either.

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 tool with no output schema and no annotations, the description is too minimal. It fails to clarify differences from sibling tools like delete_memory or remove_knowledge_base, nor does it mention any consequences, permissions, or error behavior, leaving the agent underinformed.

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 schema fully describes the only parameter (file_ids) with a clear description, and the tool description adds nothing beyond that. Since schema coverage is 100%, the parameter is adequately documented, but the description doesn't enhance understanding further.

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 a specific action ('delete') and a specific resource ('knowledge base documents'), which is distinct from sibling tools like add_kb_document or remove_knowledge_base. However, it doesn't explicitly differentiate from sibling delete operations like delete_memory, though the resource name makes it clear enough.

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 phrase 'when deleting knowledge base documents' provides only an implied context, repeating the obvious from the name. It gives no guidance on when not to use it, prerequisites, or alternatives among sibling tools.

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