akb_delete_vault

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

With no annotations, the description fully discloses the destructive behavior (permanent deletion of all vault data) and authorization requirements. It leaves no ambiguity about the tool's impact.

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?

Two sentences convey all essential information without redundancy. The description is front-loaded with the action and scope, and every sentence serves a clear purpose.

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 tool's simplicity (one parameter, destructive action), the description covers all critical aspects: what is deleted, permanence, and authorization. No additional information is necessary, and it aligns with sibling context (e.g., akb_archive_vault).

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 already describes the 'vault' parameter as 'Vault name to delete' (100% coverage). The tool description does not add new meaning to this parameter beyond restating the vault concept, so baseline 3 applies.

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's action (permanently delete a vault and all its data) and specifies the resource (vault). It lists the types of data deleted, distinguishing it from siblings like akb_archive_vault (which does not permanently delete).

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 warns that the action cannot be undone and requires owner or admin privileges, providing explicit usage context. It does not explicitly mention alternatives (e.g., archive), but the warning serves as a strong guideline.

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