delete_folder

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action without mentioning side effects, irreversibility, cascade deletions, or required permissions. For a destructive operation, this is a significant gap.

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 a single sentence with no unnecessary words. It is front-loaded with the action and resource, making it extremely concise and efficient. Every word earns its place.

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 destructive nature (delete) and lack of annotations or output schema, the description is under-specified. It does not explain what happens to the folder's contents, whether the action can be undone, or what the expected outcome is. It also doesn't clarify the resource type relative to siblings. The simplicity of the tool doesn't excuse the missing safety context.

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?

The schema has one parameter 'id' with 0% description coverage, so the description must add meaning. Saying 'by ID' clarifies that the id parameter identifies the folder, which adds some context. However, it does not explain how to obtain the ID or any format details beyond the schema type. Minimal but adequate for a single parameter.

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 'Delete a folder by ID' clearly states the verb (delete) and resource (folder), and specifies the parameter. It distinguishes from sibling delete tools like delete_password_folder by targeting the generic 'folder' resource, though it doesn't explain what a folder is. Clear but not fully differentiated.

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?

There is no guidance on when to use this tool vs alternatives. The description does not specify prerequisites (e.g., folder must be empty), nor does it clarify which type of folder (general vs password folder). No exclusions or alternative tool references are provided.

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