wordpress_bulk_create_posts

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

No annotations are provided, so the description carries full burden. It states 'Create multiple posts' which implies a write operation, but doesn't disclose behavioral traits such as required permissions, rate limits, error handling, or whether it's atomic (all-or-nothing). The efficiency note is vague and doesn't add concrete behavioral context, leaving significant gaps for a mutation tool.

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 sized and front-loaded: two concise sentences that directly state the tool's function and efficiency benefit, with zero wasted words. It's structured to convey core information immediately, making it easy for an agent to parse.

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 complexity (bulk write operation), no annotations, no output schema, and 0% schema coverage, the description is incomplete. It lacks details on behavioral aspects (e.g., permissions, limits), parameter specifics, and expected outcomes. For a tool that creates multiple posts, this minimal description fails to provide adequate context for safe and effective use.

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%, with one parameter 'posts' of type array. The description adds minimal semantics by implying 'multiple posts' but doesn't explain the structure of the array elements (e.g., post objects with fields like title, content), format, or constraints. For a bulk creation tool with undocumented parameters, this is insufficient to compensate for the coverage gap.

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's purpose: 'Create multiple posts in one operation' specifies the verb (create) and resource (posts), with 'multiple' indicating batch capability. It distinguishes from the sibling 'wordpress_create_post' by emphasizing bulk operations. However, it doesn't specify the exact scope (e.g., post types) beyond 'posts'.

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 implies usage context with 'efficient for batch content generation,' suggesting it's for bulk scenarios rather than single posts. However, it lacks explicit guidance on when to use this vs. 'wordpress_create_post' or 'wordpress_bulk_update_posts,' and doesn't mention prerequisites like authentication or permissions. The guidance is implied but not comprehensive.

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