wordpress_bulk_update_meta

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

No annotations are provided, so the description carries the full burden. It discloses batch behavior, per-item permission checks via current_user_can, deletion when null is passed, and a maximum item limit of 500. This covers key behavioral traits.

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 three sentences with no wasted words. It front-loads the core purpose and then adds constraints and behavior in a logical order.

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 simple schema (2 parameters) and no output schema or annotations, the description covers the essential behaviors: batch update, permission check, deletion via null, and limits. It could mention the response format, but it is not critical for selection or 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?

The schema has 0% description coverage, so the description must compensate. It adds that 'updates' items are permission-checked and that null meta values delete keys, but it does not describe the expected structure of the 'updates' array items or the format of the 'site' parameter. Meaning is added but incomplete.

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 batch-updates post_meta for posts, pages, and WooCommerce products using a specific companion plugin. It uses a specific verb (batch-update) and resource (post_meta), distinguishing it from sibling tools like wordpress_update_post.

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 mentions the companion plugin requirement and permission checks, but does not explicitly state when to use this tool versus alternatives (e.g., single-update tools). It provides usage context (batch updates, max 500 items) but lacks when-not-to-use guidance.

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