Delete a folder

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

Annotations already mark the tool as destructive and read-only=false, but the description adds significant behavioral context: default moves documents/subfolders up one level, deleteContents deletes them, and permission requirements. This goes beyond annotations and fully discloses consequences.

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?

Three focused sentences: the first states the action and identification method, the second explains default behavior, the third covers the deleteContents option and permissions. Every sentence adds value, and the most important info is front-loaded.

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 provides all necessary operational details: identification method, behavior with and without deleteContents, and required permission levels. For a 3-parameter tool with a simple output (no output schema), this is complete and leaves no ambiguity for an agent.

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% with descriptions for all parameters, and the description adds meaning for folderName (id or exact name) and deleteContents (default false). It clarifies that deleteContents also includes subfolders and explains the permission implications, enhancing the schema.

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 states 'Delete a sidebar folder, found by its id or exact name' with a clear verb and resource, and distinguishes it from document deletion by focusing on folders. It is specific and differentiates from siblings like delete-document and journal-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 implies when to use this tool (for deleting folders) and explains the default behavior versus deleteContents, giving clear context. It doesn't explicitly name alternatives, but the resource type is unambiguous, and it covers the main decision point (whether to also delete contents).

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