akb_create_collection

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

Discloses idempotency and return value on duplicate, as well as required role (Writer or higher). Without annotations, this adds good transparency, though it does not mention whether parent paths are created or if vault must exist.

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: one for primary purpose, one for idempotency and role. No wasted words, efficiently communicates essential information.

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 purpose, idempotency, and role. For a simple creation tool with 3 parameters and no output schema, this is reasonably complete. Missing details about parent path handling, 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?

Schema provides 100% coverage with descriptions for all parameters. The description adds no extra parameter meaning beyond idempotency context, which is already covered. Baseline 3 is appropriate.

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?

Clearly states the tool creates an empty collection (folder) inside a vault. Includes idempotency note and role requirement, distinguishing it from other creation tools like akb_create_table or akb_create_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?

Implies usage for creating collections, but does not explicitly mention when to use this tool versus alternatives like akb_put_file or akb_create_table. No when-not or alternative guidance provided.

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