akb_create_collection

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

No annotations are provided, so the description handles behavioral disclosure. It discloses idempotency (returns {created: false} if exists) and role requirement, which are key traits. It could mention whether it creates intermediate paths, but overall it is transparent enough.

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 concise with two sentences. The first sentence states the purpose, the second adds idempotency and role. No wasted words.

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 simple creation tool with 3 parameters and no output schema, the description is fairly complete. It covers purpose, behavior (idempotent), role, and param hints. One minor gap: it doesn't specify the return format on success (e.g., {created: true}) but it's implied by the idempotency detail.

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%, providing baseline value. The description adds nuance to the 'path' parameter with examples ('api-specs' or 'docs/guides'), which clarifies usage beyond the schema. The 'summary' parameter is described as 'optional one-line description', adding context.

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 verb 'Create', the resource 'empty collection (folder)', and the scope 'inside a vault'. It distinguishes from siblings like akb_create_vault and akb_create_table by specifying 'collection'.

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 mentions idempotency and the required role (Writer or higher), which are helpful usage constraints. However, it does not explicitly state when to use this tool vs alternatives or provide when-not guidance.

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