medias_bulk_delete_media_objects

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

The description is minimal and does not disclose side effects, permanence, or reversibility. Annotations already indicate readOnlyHint=false and destructiveHint=false, but the description adds no context about what actually happens to files or folders, nor about permissions or idempotency. There is no contradiction, but the burden of behavioral disclosure falls almost entirely on schema, which is vague.

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 short, consisting of only a noun-phrase. While it is concise, it is under-specified and lacks any actionable structure. It does not front-load critical information because there is almost no information at all.

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 bulk delete/trash operation, the description is grossly incomplete. It does not explain the difference between 'deleted' and 'trashed' statuses, the required format of filesToBeDeleted, potential consequences, or whether the operation is reversible. With no output schema and only vague parameter descriptions, an agent cannot confidently invoke this tool.

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 all parameters are documented in the schema itself. The description adds no parameter-specific context, but since the schema already explains each field, a baseline of 3 is appropriate. It does not compensate for any ambiguity in the schema, such as the structure of filesToBeDeleted objects.

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 states a clear action (Bulk Delete/Trash) and target (Files or Folders). It is specific enough to convey the operation, though it does not differentiate from related media tools like medias_delete_media_content or medias_bulk_update_media_objects.

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?

No guidance is provided on when to use this tool versus alternatives, nor any mention of prerequisites or conditions. The description does not help an agent decide between this and other media-related operations.

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