delete_folder

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

Annotations already indicate destructiveHint=true. The description adds that nested folders will be deleted and reports/allocations are moved to root, going beyond annotations. It does not discuss permissions or reversibility, but the destructive behavior is clearly disclosed.

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: one for context, one for the action, and one for consequences. It is efficient and front-loaded with the core purpose.

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 covers what the tool does and its key side effects for a destructive operation without output schema. It does not specify error conditions or permission requirements, but the core behavior is sufficiently explained.

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 input schema has two parameters: 'id' (required, no description) and 'customerContext' (with description). Schema description coverage is 50%. The description does not mention either parameter, so it adds no value beyond the schema for parameter understanding.

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 folder, and distinguishes it from sibling tools like create_folder or update_folder by specifying the deletion effect and consequences (nested folders deleted, contents moved to root).

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 explains what happens when the tool is used (nested folders deleted, reports/allocations moved to root), providing clear context. It does not explicitly state when not to use it or mention alternatives, but the effect is well-described.

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