Delete Folder

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

Annotations already flag destructiveHint=true and non-idempotency, but the description adds real context beyond them: the cascade deletion of contained media, the exact permission scopes required, the confirm=true mandate, and a warning about sharing access/notifications/charges. The trailing warning is somewhat generic boilerplate, keeping it from a 5.

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 core action and cascade scope are front-loaded in the first sentence, and the permission block is organized under a header. The token-scope prose is verbose but relevant for an irreversible operation.

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 delete with annotations covering the safety profile, the description covers what is destroyed, the auth requirements, and the confirmation gate. No output schema exists but a delete tool needs no return-value explanation, so the definition is nearly complete.

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 description coverage is 100%, so id, account, and confirm are all documented in the schema. The description's mention of confirm=true largely restates the schema constraint and adds no syntax or format detail beyond it; baseline 3 applies.

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?

States a specific verb and resource plus the critical scope detail that it deletes 'the media inside it', which distinguishes it from delete_subfolder and the various delete_media tools. An agent can immediately tell what this removes.

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 supplies prerequisites (required token scopes, confirm=true for the mutation) but never states when to choose this over sibling alternatives like delete_subfolder or delete_media, or any exclusion conditions. Usage is implied rather than routed.

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