wp_create_content

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

With no annotations provided, the description carries the full safety burden. It explicitly states that dry_run writes nothing, that existing slugs are skipped (idempotent), and that prod writes require allow_prod=true. This is strong transparency for a tool that can create content.

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 dense but well organized, with each sentence serving a clear purpose. The block type enumeration is necessary detail and does not feel padded.

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?

The description covers the critical workflow: dry-run behavior, item structure, SEO mapping, idempotence, and production safety. It does not describe the non-dry-run success response shape or elaborate on post_type, but it gives enough context for an agent to invoke the tool safely.

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 description explains items, seo, dry_run, and allow_prod in detail, and connects install to the required profile discovery. It does not explicitly define post_type beyond the schema default of 'page', leaving a small semantic 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 bulk-creates posts/pages and even specifies the builder context (Divi 4 / Gutenberg). It is distinct from sibling tools like wp_edit_page or wp_get_content by focusing on creation and bulk behavior.

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 gives practical usage guidance: run wp_discover_site first, dry_run is the default, and allow_prod is required for production writes. It does not explicitly name an alternative tool for single-item creation, but the context of bulk creation is clear enough.

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