wp_create_post

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

With no annotations, the description must carry behavioral disclosure. It does reveal an important prerequisite: WP_USERNAME/WP_APP_PASSWORD must be configured. This is useful operational context. However, it does not describe side effects (e.g., publishing, post status behavior), permissions, or response behavior, leaving notable gaps.

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 two short sentences with no filler or redundancy. It front-loads the core action and then gives the credential requirement. Every word earns its place.

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 mutating create tool with no annotations and no output schema, the description is too thin. It omits parameter guidance, usage boundaries, expected return value, and behavioral consequences such as whether the post is published immediately. The auth requirement is helpful but not sufficient for an agent to invoke the tool confidently.

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%, so the description must compensate for undocumented parameters. It does not mention title, status, content, required fields, or enum meanings. The schema provides only names/types, and the description adds no parameter-level meaning whatsoever.

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 states a clear verb and resource: 'Create a new WordPress post.' It is easy to understand what the tool does, and 'create' distinguishes it from the update/delete/get/list siblings. However, it does not explicitly differentiate from wp_create_page or mention the sibling set.

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?

There is no guidance about when to use this tool versus alternatives. It does not say to use this for new posts only, nor does it point to wp_update_post for edits or wp_create_page for pages. The context for choosing it over siblings is absent.

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