wordpress_advanced_bulk_delete_media

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

With no annotations provided, the description carries the full burden and successfully discloses critical behavioral traits: the operation is permanent ('permanently deletes') and has a batch size limit ('Max 100 items'). It lacks details on partial failure behavior, authentication requirements, or return values.

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 concise with three efficient sentences. It loses one point for the '[UNIFIED]' prefix, which appears to be metadata noise rather than descriptive content useful for agent decision-making.

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 destructive bulk operation with no output schema and zero schema parameter coverage, the description covers the essential safety warning (permanent deletion) and operational limits. However, it falls short of completeness due to missing parameter semantics and error handling details.

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%, and the description inadequately compensates. While 'Max 100 items' hints at the 'media_ids' array limit, the 'site' parameter (which likely specifies the target WordPress instance) and the 'force' parameter are completely unexplained.

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 tool deletes multiple media items at once, distinguishes itself from the single-item 'wordpress_delete_media' sibling via 'multiple' and the 'Max 100 items' constraint, and specifies the destructive scope ('permanently deletes files from server').

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 provides the operational constraint 'Max 100 items per request,' implying batch usage limits. However, it lacks explicit guidance on when to choose this over the single-delete alternative or prerequisites like required permissions.

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