Delete Project Folder

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

The description includes contradictory statements: 'move to recycle bin' implies potential recovery, but then says 'cannot be undone' and 'permanently delete'. Annotations already indicate destructiveHint=true, but the description adds confusion rather than clarity. It does not disclose permissions or rate limits.

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 repetitive, stating 'cannot be undone' twice and 'permanently remove documents' multiple times. It includes extraneous API endpoint details that could be omitted. The core message is buried in redundancy.

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?

For a destructive tool with no output schema, the description should clearly explain the result (e.g., return value, effect on related data). The contradictory statements about recycling vs permanent deletion create confusion. Missing usage context like permissions or irreversible consequences beyond the vague 'cannot be undone'.

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 covers 100% of parameters with clear descriptions, so the description adds no new semantic value beyond stating required parameters. The baseline score of 3 is appropriate.

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) and resource (folder). However, it does not differentiate from sibling delete folder tools like 'delete_company_folder', leaving ambiguity about which context (project vs company) this applies to.

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 mentions required parameters and a warning that the action cannot be undone, but it provides no guidance on when to use this tool versus alternatives (e.g., other delete tools). It does not specify prerequisites or when not to use it.

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