KIROK_delete_bank

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

Describes destructive nature, irreversibility, and cascade deletion of all associated data. Documents the preview behavior and the need for explicit user approval. No annotations contradict.

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?

Very concise: three short paragraphs and a bullet list of args. No unnecessary words. Front-loaded with the most critical information (destructive, permanent).

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?

Covers the full behavior: what is deleted, safety preview, user approval requirement. The output schema is mentioned as existing, so return value details are assumed covered. Slight gap: could explicitly state preview output format, but not critical.

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?

Input schema has no descriptions (0% coverage), but the description fully explains both parameters: bank_id (bank to delete) and confirm (must be true to delete, defaults to false for preview). Adds essential meaning beyond schema fields.

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 tool permanently deletes a bank and all associated data (memories, observations, models, config). This differentiates it from siblings like KIROK_clear_bank or KIROK_delete_mental_model.

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?

Provides clear two-phase usage: preview without confirm=true, actual delete only after user approval. Lacks explicit comparison to alternative tools for deletions but the safety instructions are strong.

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