akb_create_vault

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

With no annotations provided, the description carries the behavioral disclosure burden. It is transparent about the access-controlled nature of vaults, and clearly states that external_git mode tracks the remote on a polling schedule and rejects user writes. It could also note permission requirements or default visibility, but the most important behavioral traits are disclosed.

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 concise sentences, front-loaded with the main purpose and followed by the key mode distinction. There is no redundant wording or repetition of schema details.

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 the core purpose and the externally significant mode. The schema already documents all parameters, including the nested external_git object and the unusual _vault_skill_ack field. A small gap is that it does not mention what the tool returns or any permission prerequisites, but for a creation tool with a rich schema this is adequate.

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?

Schema coverage is 100%, so the baseline is 3. The description adds real semantic value by explaining that external_git changes the entire creation mode to a read-only mirror, with polling and write-rejection behavior, which is not fully obvious from the schema alone.

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 opens with a specific verb and resource: 'Create a new knowledge base vault,' and clarifies what a vault is. It also distinguishes the external_git mode from a normal vault, making it easy to separate this from sibling tools like akb_create_collection or akb_delete_vault.

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 gives concrete guidance on when to use the external_git variant: pass it to create a read-only mirror, otherwise create a standard vault. It does not explicitly name alternatives or state when not to use this tool, but the primary use case is clear from the first sentence.

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