ghl_media_bulk_delete_files

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

The description discloses the soft-delete/trash behavior, which aligns with the destructiveHint: false annotation. However, it does not add further behavioral context beyond what annotations already provide (e.g., idempotency, open-world hint). No contradiction detected.

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 concise (two sentences plus endpoint info) with no fluff. It is front-loaded with the title and verb.

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 lacks details about the response (no output schema) and does not clarify whether folders are handled differently from files. The endpoint info is extraneous for tool usage. More context would be beneficial.

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?

The input schema has 100% description coverage, so each parameter is documented. The tool description does not add extra meaning beyond the schema, meeting the baseline for high schema coverage.

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 the verb ('Bulk Delete/Trash') and the resource ('Files or Folders'). It distinguishes from siblings like ghl_media_delete_file (singular) and ghl_media_bulk_update_files (update) by specifying the bulk and soft-delete nature.

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 on when to use this tool versus alternatives. The sibling ghl_media_delete_file exists for single file deletion, but no comparison or when-not-to-use information is provided.

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