delete_knowledge

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

No annotations are provided, so the description must disclose behavioral traits. It fails to mention whether deletion is permanent, whether it cascades to related data, or whether any permissions are required. The description is purely action-oriented with no behavioral context.

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 extremely terse, but this is under-specification rather than conciseness. It provides no useful information beyond the tool name, similar to the 'Process' example in the calibration guide.

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 deletion tool with no annotations, no output schema, and a single parameter, the description should explain consequences, reversibility, and typical use cases. The current description is wholly inadequate for an agent to understand the tool's impact.

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 provides 100% coverage for the single parameter knowledge_id with description 'Knowledge ID'. Per the rubric, high schema coverage yields a baseline of 3. The description adds no additional parameter meaning but is not required to compensate.

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 'Delete knowledge' is essentially a tautology of the tool name. It states a verb and resource but does not clarify what 'knowledge' refers to (e.g., a document, chunk, or knowledge base entry). It does not distinguish from sibling tools like delete_knowledge_base or delete_chunk.

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?

There is no guidance on when to use this tool versus alternatives. The description does not mention scenarios, prerequisites, or differences from related delete tools such as delete_session or delete_chunk.

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