medias_delete_media_content

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds 'File or Folder' to clarify the resource scope, which is mildly useful but does not elaborate on consequences, reversibility, or authorization. It does not contradict annotations, so credit is given for the added context.

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 extremely concise: 'Delete File or Folder' is a single, front-loaded sentence with zero waste. It immediately communicates the action and target without any padding, which is ideal for quick comprehension.

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 is incomplete for a destructive tool. It does not explain what the 'id' parameter refers to (media content ID) nor does it distinguish this from medias_bulk_delete_media_objects, which is critical for correct selection. It also omits any mention of the permanence or the effect of altId/altType beyond schema descriptions. Given the low complexity and annotations covering safety, more guidance on usage scope is needed.

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 67%, with altId and altType having descriptions about location defaults. The description 'Delete File or Folder' does not add any parameter semantics. Since coverage is above 50%, the baseline is 3, and the description does not improve upon it.

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 'Delete File or Folder', specifying the action and resource. It is specific about what is being deleted (media content) but does not differentiate from sibling tools like medias_bulk_delete_media_objects, which also deletes media objects. This is a clear purpose but lacks sibling distinction.

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?

There is no guidance on when to use this tool vs alternatives. The description does not mention whether it handles single items, require prerequisites, or when not to use it. The existence of bulk delete siblings without any distinguishing context leaves the agent without clear usage direction.

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