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

Goes well beyond the annotations by disclosing what is actually destroyed — not just the item record but 'its stored files' — and repeats the irreversibility in plain language ('Cannot be undone'). It also pre-empts a plausible failure mode (film assets are refused), which annotations cannot express; nothing here conflicts with destructiveHint=true or idempotentHint=true.

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?

Three short sentences, front-loaded with the action and scope, then the consequence, then the exclusion. No filler and no repetition of annotation fields such as readOnlyHint.

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 two-required-param tool with no output schema, the description covers target selection, blast radius, irreversibility, and one refusal case. It does not say what happens to references pointing at the deleted asset (e.g. visuals attached to posts) or what a success response looks like, which is a modest remaining gap.

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 the schema already documents both required params and the optional user_goal. The description's 'id from list_brand_assets or list_creations' merely restates the asset_id schema description verbatim, adding no new syntax or format meaning; brand_id and user_goal are untouched. 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 ('Permanently delete ONE item from a brand's library') and enumerates the three asset kinds covered: uploads, generated visuals, logos. The capitalization of ONE and the explicit scope make it distinguishable from bulk deletes and from sibling deletes like delete_collection or delete_page.

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?

Tells the agent exactly where to source the id (list_brand_assets for uploads, list_creations for visuals/logos) and sets a clear exclusion: films are managed in Video Studio and rejected here. It stops short of naming a sibling for deleting collections or other library objects, so the negative space around non-item deletions is left implicit.

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