delete_folder

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

The description mentions 'permanently', hinting at destructive behavior, but does not disclose consequences like cascading deletion of contents, reversibility, or error conditions. With no annotations, the description carries the full burden and falls short.

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 with one sentence. It front-loads the key information, but could be structured to include more detail without losing conciseness.

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 parameter, no output schema, no annotations), the description still leaves gaps: it doesn't explain return values, error handling, or what happens to nested items. A more complete description would cover these aspects.

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 for the single parameter (folder_id) is 100% as per input schema. The description adds no additional meaning beyond the schema, so it meets the baseline but provides no extra value.

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 identifies the action (Delete) and the resource (Folder) and adds 'permanently' to indicate scope. It distinguishes from sibling tools like delete_list or delete_space by specifying the resource, though it doesn't explicitly differentiate from similar operations.

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 no guidance on when to use this tool versus alternatives (e.g., remove_guest_from_folder, delete_list). It lacks information about prerequisites, such as required permissions or whether the folder must be empty.

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