akb_delete_collection

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

With no annotations provided, the description carries full burden. It discloses that the operation cascades deletes for non-empty collections, emits a single git commit, and requires Writer role. It does not mention reversibility or error handling, but for a delete operation the transparency is adequate.

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 three sentences long, each sentence provides essential information: purpose, conditional behavior, and a behavioral note. There is no redundancy or unnecessary detail, making it very concise and well-structured.

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 delete tool with no output schema, the description covers purpose, conditions for recursive use, role requirement, and git commit behavior. It lacks explicit mention of return values or prerequisites, but overall it is sufficiently complete for an agent to invoke correctly.

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%, but the description adds value by explaining the recursive parameter's behavior (required when non-empty) and the empty case. It also mentions the git commit behavior, which is not in the schema. This enhances understanding beyond the basic parameter descriptions.

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 deletes a collection, differentiating between empty and non-empty cases. It specifies the recursive parameter requirement and the effect of cascade deletion, making the purpose very specific and distinguishable from sibling tools like akb_delete or akb_delete_file.

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 provides clear guidance on when to use the recursive parameter (for non-empty collections) and mentions the role requirement (Writer or higher). It also describes the behavior for empty collections. However, it does not explicitly compare to alternative tools or state when not to use this tool.

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