wordpress_delete_media

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

With no annotations provided, the description must carry full behavioral disclosure. It successfully explains the trash versus permanent deletion modes, but omits what happens to embedded media references in posts, whether deletions are recoverable, or required permission levels.

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 appropriately brief at two sentences with the main action front-loaded. However, the '[UNIFIED]' prefix appears to be metadata noise that does not aid agent comprehension.

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?

As a destructive tool with zero schema descriptions, no annotations, and no output schema, the description should explain return values, error states (e.g., media not found), and safety implications. These omissions make it insufficient for confident tool invocation.

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%, requiring the description to compensate. While 'permanently delete or move to trash' conceptually maps to the force parameter, the description does not explicitly connect them, nor does it explain the site or media_id parameters (e.g., whether site is a URL or ID).

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 resource (media from library), and specifies the dual behavior modes (trash vs permanent). However, it does not explicitly distinguish this single-item tool from the sibling wordpress_advanced_bulk_delete_media.

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?

The description lacks explicit guidance on when to use this versus bulk deletion alternatives, and does not clarify when to set force=true (permanent) versus allowing trash. No prerequisites or warnings are provided for this destructive operation.

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