wordpress_bulk_delete_media

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

Annotations are missing, so the description carries full burden. It only says 'Delete', implying a destructive operation, but does not disclose permanence, side effects (e.g., post attachments), error handling, or whether it requires authentication.

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?

At 4 words, the description is very concise but lacks structure and essential details. It does not front-load critical information; instead, it omits almost everything, making it insufficient for an agent to use correctly.

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?

Given the destructive nature of bulk deletion, no output schema, and no annotations, the description is severely incomplete. It does not explain parameters, return values, reversibility, or any behavioral context, leaving a dangerous 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?

The single parameter 'mediaIds' has no schema description (0% coverage). The tool description does not explain what mediaIds expects (e.g., array of numeric IDs, post IDs for attachments), leaving the agent without necessary meaning.

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 'Delete multiple media files' clearly states a specific verb (Delete) and resource (media files), and the 'multiple' distinguishes it from the sibling wordpress_delete_media (singular). However, it lacks nuance like whether deletion is permanent or to trash.

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 explicit guidance on when to use this tool versus alternatives like wordpress_delete_media or wordpress_bulk_optimize_images. The description does not mention prerequisites, context, or when not to use it.

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