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

Annotations already declare destructiveHint=true, so the safety profile is known; the description adds real value by spelling out the cascade (subfolders, contained creatives) and the conditional R2 blob deletion rule when no other creative row references the key. It does not, however, mention irreversibility/recovery, permission requirements, 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 cascade behavior is front-loaded and the required-parameter note follows efficiently. The inline EXAMPLE is somewhat redundant with the schema's required list but is short and useful for call formatting.

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, no-output-schema tool, the description covers the key risk (recursive, irreversible-by-implication cascade and orphan cleanup). It stops short of stating permissions, rollback/confirmation behavior, or what happens on partial failure, which would matter for an agent invoking a destructive operation.

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 0%, so the description must compensate. It documents folder_id (required, string, UUID format) with an example call, which is genuinely helpful, but leaves connection_context entirely undocumented in both schema and description.

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 (Delete), resource (creative folder), and the exact scope (recursively, including subfolders and contained creatives). Combined with the name, an agent can immediately distinguish it from the sibling creatives_delete (which removes a creative, not a folder) and creatives_rename_folder.

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 never says when to choose this tool over alternatives like creatives_delete, usages_list_folders, or rename_folder, nor does it state prerequisites such as folder ownership or that a confirmation step precedes it. Usage is only implied by the name and the recursive scope.

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