wordpress_advanced_bulk_update_posts

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

With no annotations provided, the description carries the full burden. It discloses the batch size limit (100), but omits other behavioral traits like whether updates are atomic, whether partial failures are possible, permission requirements, or that this is a destructive write 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?

The description is appropriately front-loaded and efficient. The '[UNIFIED]' tag is unexplained noise, but the remaining three sentences are information-dense with no redundancy—covering purpose, capabilities, and constraints.

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 bulk mutation tool with 0% schema coverage, no annotations, and no output schema, the description is minimally viable. It covers what can be updated but omits parameter formats, authentication requirements, and return value structure that would be necessary for robust agent usage.

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%, requiring the description to compensate. It successfully adds semantic meaning to the complex 'updates' object by listing supported fields (status, author, categories, tags), but provides no guidance on the 'site' string format or the 'post_ids' array structure.

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 specific action ('Update multiple posts'), the resource (posts), and distinguishes from single-update siblings via 'multiple' and the 'Max 100 posts' constraint. The '[UNIFIED]' prefix is extraneous but doesn't obscure clarity.

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?

It provides the critical constraint 'Max 100 posts per request' which defines the operational limit, but lacks explicit guidance on when to use this versus the single-update wordpress_update_post or versus bulk operations on other content types.

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