syncpen_delete_folder

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

Discloses that the folder is moved to trash and that subfolders and owned documents are also affected. However, no mention of authentication needs or whether non-owned documents in subfolders are affected. With no annotations provided, the description carries the full burden.

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 concise at 14 words, front-loading the action and scope without unnecessary words or repetition.

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?

Given the simplicity of the tool (one required parameter, no output schema), the description adequately covers the core effect. However, it could mention the return value or indicate that the operation, though soft-delete, is effectively irreversible.

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% for the single parameter 'folderId', which already has a clear description. The tool description does not add any additional semantic value beyond what is in 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 clearly states the action (delete a folder) and its scope (subfolders and owned documents), distinguishing it from sibling tools like syncpen_delete_document and syncpen_move_folder.

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?

No explicit guidance on when to use this tool versus alternatives like syncpen_move_folder or syncpen_rename_folder. The description implies usage for deletion but lacks exclusions or prerequisites.

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