wordpress_bulk_create_posts

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

The description indicates a write operation but offers no details on batch limits, error handling, partial failures, or any other behavioral aspects. With no annotations provided, the description should cover these but fails to do so.

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 brief but lacks necessary detail. It front-loads the action but does not include sufficient information to be useful, making it more underspecified than concise.

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 lack of output schema, parameter descriptions, and annotations, the description is severely incomplete. The agent cannot determine the required data format or expected behavior, making the tool nearly unusable.

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 single parameter 'posts' is an array with no schema description coverage. The description does not explain the required structure of each post (e.g., title, content, fields), leaving the agent unable to construct valid input.

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 creates multiple posts in one operation, distinguishing it from single post creation tools like wordpress_create_post. However, it does not specify whether these are standard WordPress posts or if custom post types are supported.

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 efficiency but provides no explicit guidance on when to use this tool versus alternatives like wordpress_create_post or wordpress_import_content. No conditions or exclusions are stated.

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