delete_knowledge

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

With no annotations provided, the description carries full burden. It discloses the confirmation requirement and mentions the return status. However, it does not specify irreversibility, side effects, permission needs, or error conditions, leaving gaps in behavioral understanding.

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 structured with a title, paragraph, and Args/Returns sections. It is concise but has slight redundancy (first two sentences restate the same action). Overall efficient and clearly formatted.

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 the simple operation (delete) with two parameters and an output schema, the description covers essential aspects: action, parameter roles, confirmation, and return status. Minor omission: irreversibility or permanence could be mentioned.

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?

Despite 0% schema coverage, the description adds significant meaning: 'topic' is the topic name to delete, and 'confirm' must be True. This goes beyond the schema's title-only definitions, making parameter usage clear.

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 specific verb 'delete' and resource 'knowledge topic', clearly stating it removes a topic from the knowledge base. It distinguishes itself from sibling tools like save, list, get, and search, which are the only operations available for knowledge topics.

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 explicitly states that confirmation is required ('Must be True to execute the deletion'), providing clear usage guidance. However, it does not mention when to use this tool versus alternatives, though as the only delete tool, this is less critical.

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