delete_knowledge

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

With no annotations provided, the description carries the burden of disclosing behavioral traits. It states that confirmation (confirm=True) is required, which adds transparency. However, it does not mention irreversibility, permissions needed, or potential side effects, leaving gaps.

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 concise, with two sentences and a parameter list. It is front-loaded with the purpose and includes only essential information. No unnecessary words or 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?

The description covers basic functionality and parameter meaning, but given the existence of an output schema (context signal) and the simplicity of the tool, it lacks details on error handling, prerequisites (e.g., topic must exist), and irreversibility. It is minimally complete but could be more thorough.

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 has 0% description coverage, but the tool description explains each parameter: topic is the name to delete, and confirm must be True to execute. This adds meaning beyond the schema's type and default, effectively compensating for the lack of schema descriptions.

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 "Delete a saved knowledge topic" and "Removes a topic from the knowledge base," using a specific verb and resource. This distinguishes it clearly from sibling tools like save_knowledge, get_knowledge_topic, and list_knowledge.

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 does not provide any guidance on when to use this tool versus alternatives. It only mentions that confirmation is required, but lacks context on prerequisites, error conditions, or comparisons to other knowledge tools.

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