cleanup_media

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

The description only says 'Bulk delete media assets' without disclosing behavioral traits such as irreversibility, impact on existing posts that may reference the media, permission requirements, or whether the deletion is permanent. With no annotations provided, the description carries the full burden but fails to convey critical safety information for a destructive operation.

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 at six words and is front-loaded with the action. However, its brevity omits essential usage and safety details, making it under-specified rather than optimally concise. A slightly longer description could include necessary context without losing efficiency.

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 operation with no annotations, no output schema, and minimal parameter detail, the description is incomplete. It does not address effects, prerequisites, or error behavior. The presence of sibling tools like list_media and delete_post suggests that more context about scope (e.g., which workspace or account) and relationship to posts 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?

The schema defines a single 'media_ids' array, but the description does not explain that these are the IDs of media to delete, nor any constraints (e.g., format, count, or association with a specific workspace/account). With schema description coverage at 0%, the description should compensate for this gap but does not.

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 action ('delete') and the target resource ('media assets'), with 'bulk' indicating multiple items. This distinguishes it from sibling tools like delete_post (for posts) and upload_media_file (for uploads), though it lacks detail on what exactly qualifies as a media asset.

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 usage guidance is provided. There is no mention of when to use this tool, prerequisites, or alternatives. It does not compare to cleanup of posts or uploads, and the context of bulk deletion is left entirely to the user's interpretation.

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