WordPress: Bulk update meta

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

Annotations already flag destructive=true, idempotent=false, readOnly=false, and the description adds genuinely new behavior: per-item PHP permission checks via current_user_can('edit_post', post_id), null value deletes the key, and a 500-item ceiling. It stops short of saying whether partial failures roll back or how per-item results are reported, which matters for a destructive bulk write.

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?

Four dense sentences, each carrying a distinct fact (scope, transport, permission model, delete semantics, limit), with the resource named up front. No filler, though the '[UNIFIED]' prefix and plugin name consume leading attention without aiding selection.

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 mutation with an opaque schema and no output schema, the description covers prerequisites, limits and delete semantics but omits the item structure and the return/partial-failure behavior. An agent knows the guardrails but not how to build the payload or interpret results.

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 coverage is 0% and the 'updates' array is typed only as a bare array with no item schema, so the description is the only place the item shape could be explained — and it is not. It hints that an item has a meta value where null means delete, but never names post_id, meta_key, or meta_value fields, leaving the caller unable to construct a valid item without guessing.

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?

States a specific verb and resource ('Batch-update post_meta') and scopes the object types it applies to (posts, pages, WooCommerce products). An agent can tell this mutates metadata rather than post bodies, which distinguishes it from the sibling bulk post-update tool, though it never names the alternative explicitly.

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?

Gives a hard prerequisite (airano-mcp-bridge v2.2.0+) and a volume cap (500 items per call), which shapes when the tool is viable. However, there is no guidance on when to pick this over wordpress_update_post or wordpress_specialist_wp_bulk_post_update; the agent must infer that this is for many small meta edits.

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