wp_create_post

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

With no annotations, the description mentions 'comprehensive validation and detailed success feedback including management links,' but lacks disclosure of authentication needs, rate limits, or potential destructive actions. It adds some behavioral context but not enough for complete transparency.

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 efficiently front-loaded with a clear statement and followed by structured examples. While the examples are extensive, they are relevant and well-organized. A minor improvement would be to condense slightly.

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?

Despite 9 parameters and no output schema, the description does not explain the return format or how the 'success feedback' is structured. It lacks details on what the agent can expect after invocation, which is a gap given the tool's complexity.

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 schema coverage is 100%, and the description enriches parameter understanding with practical examples, such as 'use 0 to remove featured media' and ISO 8601 date format. This adds significant value beyond the schema.

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 explicitly states 'Creates a new WordPress post' with a specific verb and resource. Among siblings like wp_create_page and wp_create_category, the tool is clearly for posts, and the title reinforces this.

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 provides multiple usage examples covering various scenarios (draft, scheduled, featured image), offering clear context. However, it does not explicitly state when to avoid this tool or mention alternatives like wp_create_page for pages.

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