wordpress_bulk_delete_media

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

With no annotations, the description discloses that it issues N requests with a concurrency cap, uses the standard DELETE endpoint, and returns processed/errors/total. Does not elaborate on force parameter behavior or partial failure handling, but overall provides good transparency for a bulk 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?

Description is concise with three sentences, front-loading the action and resource. The '[UNIFIED]' prefix is unnecessary but not harmful. No wasted words.

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?

Covers purpose, limits, and basic behavior, but lacks details on force parameter semantics, exact return structure, error handling, and authentication prerequisites. For a bulk tool with no output schema and many sibling tools, more completeness 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?

Schema description coverage is 0%, so the description must compensate. It only indirectly addresses media_ids via the 100-limit hint. Parameters 'site' and 'force' are not explained; 'force' is only loosely tied to the 'trash or permanently remove' phrase. Missing parameter details despite needing them.

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 (trash or permanently remove) a list of media attachments in a single call,' specifying the verb, resource, and bulk scope. It distinguishes from the singular delete sibling by emphasizing 'list' and 'single call,' but does not explicitly name the alternative tool.

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?

Provides clear limits: 'Max 100 IDs per request,' concurrency cap, and client-side pagination for large lists. Explains that no companion plugin is needed. Does not explicitly state when not to use, but the context strongly implies singular deletion for single items.

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